lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Fehling (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-10733) Rule-based Replica Placement not working correct
Date Tue, 06 Jun 2017 13:37:18 GMT

    [ https://issues.apache.org/jira/browse/SOLR-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038898#comment-16038898
] 

Bernd Fehling edited comment on SOLR-10733 at 6/6/17 1:36 PM:
--------------------------------------------------------------

OK, sorry, I was just trying to explaining how the "counting" of replicas in the code is written.
The code says:
- you have a number of shards (like slots, buckets or whatelse)
- you have a counter for replicas
- you have a number of nodes (e.g. with "attributes" like port, rack, ...)
- you have rules
It selects the first slot of available shards, takes the first node from the list of nodes,
checks the node aginst all rules and, if all rules pass, assigns the node to that shard slot
*and* also increases the replica counter for that shard.
This behaviour of the code makes replica counter a node counter for the shard.
Or not?



was (Author: befehl):
OK, sorry, I was just trying to explaining how the "counting" of replicas in the code is written.
The code says:
- you have a number of shards (like slots, buckets or whatelse)
- you have a count of replicas
- you have a number of nodes (e.g. with "attributes" like port, rack, ...)
- you have rules
It selects the first slot of available shards, takes the first node from the list of nodes,
checks the node aginst all rules and, if all rules pass, assigns the node to that shard slot
*and* also increases the replica count for that shard.
This behaviour of the code makes replica counter a node counter for the shard.
Or not?


> Rule-based Replica Placement not working correct
> ------------------------------------------------
>
>                 Key: SOLR-10733
>                 URL: https://issues.apache.org/jira/browse/SOLR-10733
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Rules, SolrCloud
>    Affects Versions: 6.5.1
>            Reporter: Bernd Fehling
>            Assignee: Noble Paul
>         Attachments: SOLR-10733.patch, SOLR-10733.patch
>
>
> A setup of a SolrCloud with 6 nodes on 3 server e.g.:
> {code}
> server1:8983 , server1:7574
> server2:8983 , server2:7574
> server3:8983 , server3:7574
> {code}
> and a command for creating a new collection with rule:
> {code}
> http://localhost:8983/solr/admin/collections?action=CREATE&name=boss&
> collection.configName=boss_configs&numShards=3&replicationFactor=2&
> maxShardsPerNode=1&rule=shard:shard1,replica:<2,port:8983
> {code}
> should create a collection with 3 shards and least a shard1 with two different nodes
running on port 8983.
> {code}
> shard1 --> server_x:8983 ,  server_y:8983
> {code}
> A even more restrictive rule like
> {code}
> rule=shard:shard1,replica:<2,port:8983&rule=shard:shard3,replica:<2,port:7574
> {code}
> should also resolve to a solution because if it really checks all permutations accross
shards/replicas/ports and available nodes it should be able to solve this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message