Re: possible to dump "routing table" from a single Solr node?

2016-02-03 Thread Shawn Heisey
On 2/3/2016 11:49 AM, Ian Rose wrote:
> I'm having a situation where our SolrCloud cluster often gets into a bad
> state where our solr nodes frequently respond with "no servers hosting
> shard" even though the node that hosts that shard is clearly up.  We
> suspect that this is a state bug where some servers are somehow ending up
> with an incorrect view of the network (e.g. which nodes are up/down, which
> shards are hosted on which nodes).  Is it possible to somehow get a "dump"
> of the current "routing table" (i.e. documents with prefixes in this range
> in this collection are stored in this shard on this node)?  That would help
> immensely when debugging.

The clusterstate (in zookeeper) has this information.  You can see the
zookeeper database within the Solr admin UI by clicking on Cloud and
then Tree.

In 4.x Solr versions (and when upgrading from 4.x to 5.x) the
clusterstate is maintained in a single "clusterstate.json" file at the
root of the SolrCloud information in zookeeper.  In 5.x, each collection
has its own "state.json" file.

It is possible to gather this information programmatically with HTTP.  I
do not remember the exact URLs, but you can find them by watching what
the admin UI does in your browser's dev console.

Thanks,
Shawn



possible to dump "routing table" from a single Solr node?

2016-02-03 Thread Ian Rose
Hi all,

I'm having a situation where our SolrCloud cluster often gets into a bad
state where our solr nodes frequently respond with "no servers hosting
shard" even though the node that hosts that shard is clearly up.  We
suspect that this is a state bug where some servers are somehow ending up
with an incorrect view of the network (e.g. which nodes are up/down, which
shards are hosted on which nodes).  Is it possible to somehow get a "dump"
of the current "routing table" (i.e. documents with prefixes in this range
in this collection are stored in this shard on this node)?  That would help
immensely when debugging.

Thanks!
- Ian