[
https://issues.apache.org/jira/browse/SOLR-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789089#comment-13789089
]
Federico Piai commented on SOLR-5303:
-
OK I'm sorry for the false positive. What actually confused me is that
numShards must be passed as system property (with -D option) while for instance
solr.home can be passed this way or as an environment variable (eg in Tomcat's
context.xml). I tried to put numShards in context.xml of SolR but it did not
work.
Thank you for your answer.
numShards property is not properly taken into account
-
Key: SOLR-5303
URL: https://issues.apache.org/jira/browse/SOLR-5303
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 4.2, 4.3.1
Environment: SolR on 3 VMs each with an external Zookeeper,
multi-core startups
Reporter: Federico Piai
Labels: shard, solrcloud, zookeeper
It looks like the 'numShards' argument is ignored by SolR. The number of
shards is always defaulted to 1 unless cores are dynamically created with
Collection API.
I had this log :
INFO: numShards not found on descriptor - reading it from system property, I
looked for the piece of code where the log was located
((https://svn.apache.org/repos/asf/lucene/dev/trunk/solr/core/src/java/org/apache/solr/cloud/ZkController.java))
and I found a possible error :
log.info(numShards not found on descriptor - reading it from system
property);
numShards = Integer.getInteger(ZkStateReader.NUM_SHARDS_PROP);
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
