Timothy Potter created SOLR-7039:
------------------------------------
Summary: First collection created with stateFormat=2 results in a
weird /clusterstate.json
Key: SOLR-7039
URL: https://issues.apache.org/jira/browse/SOLR-7039
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 5.0
Reporter: Timothy Potter
Priority: Blocker
Fix For: 5.0
With the 5.0 branch, when I do:
{code}
bin/solr -c && bin/solr create -c foo
{code}
The {{/clusterstate.json}} in ZK has and invalid definition of the foo
collection
{code}
{"foo":{
"replicationFactor":"1",
"router":{"name":"compositeId"},
"maxShardsPerNode":"1",
"autoAddReplicas":"false",
"shards":{"shard1":{
"range":"80000000-7fffffff",
"state":"active",
"replicas":{}}}}}
{code}
To verify this isn't the UI sending back the wrong data, I went into the
zkCli.sh command-line and got:
{code}
[zk: localhost:9983(CONNECTED) 2] get /clusterstate.json
{"foo":{
"replicationFactor":"1",
"router":{"name":"compositeId"},
"maxShardsPerNode":"1",
"autoAddReplicas":"false",
"shards":{"shard1":{
"range":"80000000-7fffffff",
"state":"active",
"replicas":{}}}}}
cZxid = 0x20
ctime = Mon Jan 26 14:56:44 MST 2015
mZxid = 0x65
mtime = Mon Jan 26 14:57:16 MST 2015
pZxid = 0x20
cversion = 0
dataVersion = 1
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 247
numChildren = 0
{code}
The {{/collections/foo/state.json}} looks correct:
{code}
{"foo":{
"replicationFactor":"1",
"router":{"name":"compositeId"},
"maxShardsPerNode":"1",
"autoAddReplicas":"false",
"shards":{"shard1":{
"range":"80000000-7fffffff",
"state":"active",
"replicas":{"core_node1":{
"core":"foo_shard1_replica1",
"base_url":"http://192.168.1.2:8983/solr";,
"node_name":"192.168.1.2:8983_solr",
"state":"active",
"leader":"true"}}}}}}
{code}
Here's the weird thing ... If I create a second collection using the same
script, all is well and /clusterstate.json is empty
{code}
bin/solr create -c foo2
{code}
Calling this a blocker because 5.0 can't be released with this happening.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
