: In Solr 1.4, on slave, I supplied a masterUrl, but did NOT supply any : pollInterval at all on slave. I did NOT supply an "enable" : "false" in slave, because I think that would have prevented even manual : replication.
that exact same config should still work with solr 4.3 : This seemed to result in the slave never polling, although I'm not sure if : that was just an accident of Solr implementation or not. Can anyone say if it's intentional. : the same thing would happen in Solr 4.3? If I look at the admin screen for my : slave set up this way in Solr 4.3, it does say "polling enabled", but I : realize that doesn't neccesarily mean any polling will take place, since I've : set no pollInterval. correct. : In Solr 1.4 under this setup, I could go to the slave's admin/replication, and : there was a "replicate now" button that I could use for manually triggered : replication. This button seems to no longer be there in 4.3 replication admin Hmmm... there should be a giant blue "Replicate Now" button just below the "Refresh Status" button and just above the "Disable (or Enable) Polling" button. But this button will only appear for collections where replication is configured with a slave section (and has a masterUrl). If the master is down, the button goes away (and you get an "invalid_master" error in the UI). If it's not configured as a slave, the button never appears, because it has no idea what host to pull from if you clicked it. If you aren't seeing this button on your slave, then can you please provide... * your slave config * your master config * the output of /replication?command=details from your slave * the output of /replication?command=details from your master * your browser details * a screenshot of what your replication screen looks like on the slave? ...since attachments don't really work well with th mailing list, i would suggest open a Jira and attaching these details -Hoss
