On Jul 29, 2013, at 12:49 PM, Katie McCorkell wrote:
> I didn't think so
> since it didn't show up as yellow "recovering" on the visual display, but
> after quite a while it went from "Down" to "Active" . Thanks!
Thanks, I think we should improve this! We should publish a recovery state when
r
I am using Solr 4.3.1 . I did hard commit after indexing.
I think you're right that the node was still recovering. I didn't think so
since it didn't show up as yellow "recovering" on the visual display, but
after quite a while it went from "Down" to "Active" . Thanks!
On Fri, Jul 26, 2013 at 7:5
Can you also let me know what version of Solr are you on?
On Sat, Jul 27, 2013 at 8:26 AM, Anshum Gupta wrote:
> Hi Katie,
>
> 1. First things first, I would strongly advice to manually update/remove
> zk or any other info when you're running things in the SolrCloud mode
> unless you are sure of
Hi Katie,
1. First things first, I would strongly advice to manually update/remove zk
or any other info when you're running things in the SolrCloud mode unless
you are sure of what you're doing.
2. Also, your node could be currently recovering from the transaction
log(did you issue a hard commit
Hello,
I am using the SolrCloud with a zookeeper ensemble like on example C from
the wiki except with total of 3 shards and no replicas (oops). After
indexing a whole bunch of documents, shard 2 went down and I'm not sure
why. I tried restarting it with the jar command and I tried deleting shard1
