HI Erick,
Yes. clusterstate.json is available in /solr path (i.e
/solr/clusterstate.json)
As Shawn said, client might be starting on different zknode. :(
Thanks,
Anil
On 11 June 2018 at 20:29, Erick Erickson wrote:
> _where_ is clusterstate.json? The connection string adds a solr
> prefix, so
On 6/11/2018 8:35 AM, Anil wrote:
> for failure could be #1. but not sure why client started with different
> zkHost. i used 127.0.01:2181/solr itself. zk nodes started with
> 127.0.0.1:2181, 2182, 2183
> is there anyway i can figure this out and correct it ? Thanks.
I suspect that the difference
_where_ is clusterstate.json? The connection string adds a solr
prefix, so when you look at Zookeeper it should be in
/solr/clusterstate.json rather than /clusterstate.json.
When you use a different Zookeeper root, you need to use the exact
same root on all your operations.
As Shawn says, cluster
HI Shawn,
Thanks for response. please find comments in the context.
Thanks,
Anil
On 11 June 2018 at 19:06, Shawn Heisey wrote:
> On 6/11/2018 6:41 AM, Anil wrote:
>
>> I was trying solrcloud cluster setup using solr 7.3.1 and it is up. Admin
>> console looks good and queries in console are wo
On 6/11/2018 6:41 AM, Anil wrote:
I was trying solrcloud cluster setup using solr 7.3.1 and it is up. Admin
console looks good and queries in console are working fine. But solrj
connection failing with following exception
org.apache.solr.common.SolrException: Cannot connect to cluster at
127.0.0
