Re: ClusterStateMutator

2017-01-05 Thread Hendrik Haddorp
The UI warning was quite easy to resolve. I'm currently testing Solr with HDFS but for some reason the core ended up on the local storage of the node. After a delete and restart the problem was gone. On 05.01.2017 12:42, Hendrik Haddorp wrote: Right, I had to do that multiple times already when

Re: ClusterStateMutator

2017-01-05 Thread Hendrik Haddorp
Right, I had to do that multiple times already when I restarted nodes during collection creation. In such cases I was left with data in the clusterstate.json, which at least on 6.2.1, blocked further collection creations. Once manually deleted or set to {} collection creation worked again. Se

Re: ClusterStateMutator

2017-01-04 Thread Erick Erickson
Let us know how it goes. You'll probably want to remove the _contents_ of clusterstate.json and just leave it as a pair of brackets , i.e. {} if for no other reason than it's confusing. Times past the node needed to be there even if empty. Although I just tried removing it completely on 6x and I w

Re: ClusterStateMutator

2017-01-04 Thread Hendrik Haddorp
Hi Erik, I have actually also seen that behavior already. So will check what happens when I set that property. I still believe I'm getting the clusterstate.json set already before the node comes up again. But I will try to verify that further tomorrow. thanks, Hendrik On 04/01/17 22:10, Erick Er

Re: ClusterStateMutator

2017-01-04 Thread Erick Erickson
Hendrik: Historically in 4.x, there was code that would reconstruct the clusterstate.json code. So you would see "deleted" collections come back. One scenario was: - Have a Solr node offline that had a replica for a collection. - Delete that collection - Bring the node back - It would register it

Re: ClusterStateMutator

2017-01-04 Thread Hendrik Haddorp
You are right, the code looks like it. But why did I then see collection data in the clusterstate.json file? If version 1 is not used I would assume that no data ends up in there. When explicitly setting the state format 2 the system seemed to behave differently. And if the code always uses version

Re: ClusterStateMutator

2017-01-04 Thread Shalin Shekhar Mangar
Actually the state format defaults to 2 since many releases (all of 6.x at least). This default is enforced in CollectionsHandler much before the code in ClusterStateMutator is executed. On Wed, Jan 4, 2017 at 6:16 PM, Hendrik Haddorp wrote: > Hi, > > in > solr-6.3.0/solr/core/src/java/org/apache