You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Amrit Sarkar (JIRA)" <ji...@apache.org> on 2019/02/06 11:29:00 UTC

[jira] [Updated] (SOLR-13226) Add note in Node Added Trigger documentation in Autoscaling

     [ https://issues.apache.org/jira/browse/SOLR-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amrit Sarkar updated SOLR-13226:
--------------------------------
    Description: 
Node Added Trigger doesn't abide by SOFT rules [strict: false] and results in abnormal cluster operational behavior.

Let's say; we wish to do the following:
1. Not more than 10 cores reside on Single node.
2. Wish to distribute the cores, replicas equally to each Node.

If we go by the following policy:

not more than one replica for unique shard on a node. not a strict rule.
{code}
  {"replica":"<2", "shard": "#EACH", "node": "#ANY", "strict": false},
{code}
distribute the replicas equally across the nodes, not a strict rule.
{code}
  {"replica": "#EQUAL", "node": "#ANY", "strict": false},
{code}
not more than 10 cores allowed on a single node, strict rule.
{code}
  {"cores": "<10", "node": "#ANY"}
{code}
cluster state ends up like:

Screenshot -1

Only the strict rule is followed and multiple replicas are added to single Solr node, as rules are not strict – _{"replica":"<2", "shard": "#EACH", "node": "#ANY", "strict": false}_

While the following with all strict rule generate normal operational behavior, add a replica to each shard of collection 'wiki' :
{code}
[
  {"replica":"<2", "shard": "#EACH", "node": "#ANY"},
  {"replica": "#EQUAL", "node": "#ANY"},
  {"cores": "<10", "node": "#ANY"}
  ]
{code}

Screenshot -2

This behavior should be documented.

  was:
Node Added Trigger doesn't abide by SOFT rules [strict: false] and results in abnormal cluster operational behavior.

Let's say; we wish to do the following:
1. Not more than 10 cores reside on Single node.
2. Wish to distribute the cores, replicas equally to each Node.

If we go by the following policy:

not more than one replica for unique shard on a node. not a strict rule.
{code}
  {"replica":"<2", "shard": "#EACH", "node": "#ANY", "strict": false},
{code}
distribute the replicas equally across the nodes, not a strict rule.
{code}
  {"replica": "#EQUAL", "node": "#ANY", "strict": false},
{code}
not more than 10 cores allowed on a single node, strict rule.
{code}
  {"cores": "<10", "node": "#ANY"}
{code}
cluster state ends up like:

Screenshot -1

Only the strict rule is followed and multiple replicas are added to single Solr node, as rules are not strict – _{"replica":"<2", "shard": "#EACH", "node": "#ANY", "strict": false}_

While the following with all strict rule generate normal operational behavior, add a replica to each shard of collection 'wiki' :
{code}
[
  {"replica":"<2", "shard": "#EACH", "node": "#ANY"},
  {"replica": "#EQUAL", "node": "#ANY"},
  {"cores": "<10", "node": "#ANY"}
  ]
{code}

This behavior should be documented.


> Add note in Node Added Trigger documentation in Autoscaling
> -----------------------------------------------------------
>
>                 Key: SOLR-13226
>                 URL: https://issues.apache.org/jira/browse/SOLR-13226
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>            Reporter: Amrit Sarkar
>            Priority: Major
>         Attachments: Screen Shot 2019-02-05 at 3.55.31 AM.png, Screen Shot 2019-02-05 at 4.02.00 AM.png
>
>
> Node Added Trigger doesn't abide by SOFT rules [strict: false] and results in abnormal cluster operational behavior.
> Let's say; we wish to do the following:
> 1. Not more than 10 cores reside on Single node.
> 2. Wish to distribute the cores, replicas equally to each Node.
> If we go by the following policy:
> not more than one replica for unique shard on a node. not a strict rule.
> {code}
>   {"replica":"<2", "shard": "#EACH", "node": "#ANY", "strict": false},
> {code}
> distribute the replicas equally across the nodes, not a strict rule.
> {code}
>   {"replica": "#EQUAL", "node": "#ANY", "strict": false},
> {code}
> not more than 10 cores allowed on a single node, strict rule.
> {code}
>   {"cores": "<10", "node": "#ANY"}
> {code}
> cluster state ends up like:
> Screenshot -1
> Only the strict rule is followed and multiple replicas are added to single Solr node, as rules are not strict – _{"replica":"<2", "shard": "#EACH", "node": "#ANY", "strict": false}_
> While the following with all strict rule generate normal operational behavior, add a replica to each shard of collection 'wiki' :
> {code}
> [
>   {"replica":"<2", "shard": "#EACH", "node": "#ANY"},
>   {"replica": "#EQUAL", "node": "#ANY"},
>   {"cores": "<10", "node": "#ANY"}
>   ]
> {code}
> Screenshot -2
> This behavior should be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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