Re: 1.4.1 replication failure is still 200 OK

2011-02-23 Thread Markus Jelsma
Hi, I'd guess a non-200 HTTP response code would be more appropriate indeed but it's just a detail. A successful replication will change a few things on the slave: - increment of generation value - updated indexVersion value - lastReplication will have a new timestamp You can also check for a r

1.4.1 replication failure is still 200 OK

2011-02-23 Thread Jonathan Rochkind
Should this be considered a bug, or is there something i"m missing? Let's say I have a replication slave set up, but without polling. So I'm going to manually trigger replication. So I do that: http://example.org/solr/core/replication?command=fetchIndex I get a 200 OK _even if_ the masterUrl