[
https://issues.apache.org/jira/browse/SOLR-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558131#comment-13558131
]
Brett Hoerner commented on SOLR-4321:
-------------------------------------
Here are some logs from the very first boot of this cluster (repeatable).
"default" is in solr.xml to start, I try creating test1, test2, etc using the
same curl command from above (which works fine in 4.0):
Jan 19, 2013 11:37:05 PM org.apache.solr.core.SolrCore initIndex
WARNING: [default] Solr index directory '/mnt/solr/data/default/index' doesn't
exist. Creating new index...
Jan 19, 2013 11:45:18 PM org.apache.solr.core.SolrCore initIndex
WARNING: [test1_shard2_replica2] Solr index directory
'/mnt/solr/data/test1_shard2_replica2/index' doesn't exist. Creating new
index...
Jan 19, 2013 11:45:19 PM org.apache.solr.common.SolrException log
SEVERE: Sync Failed
Jan 19, 2013 11:48:29 PM org.apache.solr.core.SolrCore initIndex
WARNING: [test2_shard2_replica2] Solr index directory
'/mnt/solr/data/test2_shard2_replica2/index' doesn't exist. Creating new
index...
Jan 19, 2013 11:48:29 PM org.apache.solr.common.SolrException log
SEVERE: Sync Failed
Jan 19, 2013 11:48:31 PM org.apache.solr.core.SolrCore initIndex
WARNING: [test3_shard1_replica1] Solr index directory
'/mnt/solr/data/test3_shard1_replica1/index' doesn't exist. Creating new
index...
Jan 19, 2013 11:48:32 PM org.apache.solr.common.SolrException log
SEVERE: Sync Failed
Jan 19, 2013 11:48:34 PM org.apache.solr.core.SolrCore initIndex
WARNING: [test4_shard2_replica1] Solr index directory
'/mnt/solr/data/test4_shard2_replica1/index' doesn't exist. Creating new
index...
Jan 19, 2013 11:48:34 PM org.apache.solr.core.SolrCore initIndex
WARNING: [test4_shard1_replica2] Solr index directory
'/mnt/solr/data/test4_shard1_replica2/index' doesn't exist. Creating new
index...
Jan 19, 2013 11:48:36 PM org.apache.solr.common.SolrException log
SEVERE: Sync Failed
Jan 19, 2013 11:48:37 PM org.apache.solr.core.SolrCore initIndex
WARNING: [test5_shard2_replica2] Solr index directory
'/mnt/solr/data/test5_shard2_replica2/index' doesn't exist. Creating new
index...
Jan 19, 2013 11:48:39 PM org.apache.solr.common.SolrException log
SEVERE: Sync Failed
Jan 19, 2013 11:48:41 PM org.apache.solr.update.PeerSync sync
WARNING: no frame of reference to tell of we've missed updates
Jan 19, 2013 11:50:07 PM org.apache.solr.core.SolrCore initIndex
WARNING: [foo_shard1_replica1] Solr index directory
'/mnt/solr/data/foo_shard1_replica1/index' doesn't exist. Creating new index...
Jan 19, 2013 11:50:08 PM org.apache.solr.common.SolrException log
SEVERE: Sync Failed
> SolrCloud collection CREATE will put multiple master shards on a single node
> (and no shards on some)
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-4321
> URL: https://issues.apache.org/jira/browse/SOLR-4321
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.1
> Reporter: Brett Hoerner
>
> This is best described by a photo of my SolrCloud admin:
> http://i.imgur.com/hW4xnxy.png
> I have a 4 node cluster, with shard count of 2 and replication factor of 2.
> After running something like,
>
> http://localhost:8983/solr/admin/collections?action=CREATE&name=15724&numShards=2&replicationFactor=2
> The shards seem to be completely randomly placed, which is fine, but some
> nodes receive more of the share than others (some even receiving none).
> For example, 15724 has given node "backfill-1d" 2 "parts",
> 15724_shard1_replica2 and 15724_shard2_replica1 but has given "backfill-2d"
> nothing at all.
> This creates unnecessary load on some nodes, no? Is this something I am
> supposed to handle myself (I looked, but don't see how).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
