Thanks for clarifying
On Thu, Aug 6, 2015 at 6:43 PM, Shawn Heisey wrote:
> On 8/6/2015 6:50 AM, Suma Shivaprasad wrote:
> > I was having issues since I am using a solr 4.8.1 client to talk to a
> 5.2.1
> > server. There is no API in ZKStateReader as well to add a collection to
> > watch in the
On 8/6/2015 6:50 AM, Suma Shivaprasad wrote:
> I was having issues since I am using a solr 4.8.1 client to talk to a 5.2.1
> server. There is no API in ZKStateReader as well to add a collection to
> watch in the 4.8.1 API . I assume that would have caused the
> clusterstate.json to be updated?
>
>
I was having issues since I am using a solr 4.8.1 client to talk to a 5.2.1
server. There is no API in ZKStateReader as well to add a collection to
watch in the 4.8.1 API . I assume that would have caused the
clusterstate.json to be updated?
Since I am using a third party library (which in turn de
The API shouldn't be changing, did you run into any errors?
Don't bother to raise a JIRA, I checked through IM and the
/clusterstate.json is still being used as a watch point for things
like creating collections, and there are other JIRAs afoot that will
take care of this at the at the right time.
Thanks Shawn.
Does this mean in client code, wherever we are using the API
"ZkStateReader.getClusterState.getCollections" to get status should be
changed to
"CollectionsAdminRequest.ClusterStatus" for each collection or will that
API continue to work ?
Thanks
Suma
On Wed, Aug 5, 2015 at 11:00 P
On 8/5/2015 9:22 AM, Suma Shivaprasad wrote:
> Hello,
>
> Is /clusterstate.json in Zookeeper updated with collection state if a
> collection is created with server running in Solr Cloud mode without
> creating a core through coreAdmin or providing a core.properties . I find
> that there is a "state
Thanks for your response. What version of solr is this change effective
from?
Will raise a jira.
Thanks
Suma
On Wed, Aug 5, 2015 at 10:37 PM, Erick Erickson
wrote:
> Yes. The older-style ZK entity was all-in-one
> in /clusterstate.json. Recently we've moved
> to a per-collection state.json inst
Yes. The older-style ZK entity was all-in-one
in /clusterstate.json. Recently we've moved
to a per-collection state.json instead, to avoid
the "thundering herd" problem. In that state,
/clusterstate.json is completely ignored and,
as you see, not updated.
Hmmm, might be worth raising a JIRA to rem
