[
https://issues.apache.org/jira/browse/SOLR-11523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-11523:
------------------------------
Description:
It is possible that the cluster is operating sub optimally with more nodes than
required. It is not possible for Solr to automatically identify a suboptimal
utilization of nodes. We expect the user to provide us with policy rules to
identify it
examples:
{code:java}
{"cores" : ">2", "node":"#ANY" , "strict" : false }
{"freedisk" : "<10", "node":"#ANY" , "strict": false}
{code}
Solr would go through all these rules to identify if it breaks any such rules.
If yes, it would go through the following steps
# Identify all violations to such rules
# Sort all nodes and identify the least loaded nodes
# If there is an empty node
## store that node name
## Simulate removal of that node and go to step #1
# Check if they are violating these rules
# if yes, simulate moving them to other nodes with more load
# if it is possible, to move without breaking rules,
## store that suggestion
## Go to step #1
# If not possible, get the list of move operations (step #6.1) and collect the
list of nodes to be removed ( step # 3.1)
was:
It is possible that the cluster is operating sub optimally with more nodes than
required. It is not possible for Solr to automatically identify a suboptimal
utilization of nodes. We expect the user to provide us with policy rules to
identify it
examples:
{code}
{"cores" : ">2", "node":"#ANY" , "strict" : false }
{"freedisk" : "<10", "node":"#ANY" , "strict": false}
{code}
Solr would go through all these rules to identify if it breaks any such rules.
If yes, it would go through the following steps
# Evaluate
> suggestions to remove nodes
> ---------------------------
>
> Key: SOLR-11523
> URL: https://issues.apache.org/jira/browse/SOLR-11523
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Noble Paul
> Priority: Major
>
> It is possible that the cluster is operating sub optimally with more nodes
> than required. It is not possible for Solr to automatically identify a
> suboptimal utilization of nodes. We expect the user to provide us with
> policy rules to identify it
> examples:
> {code:java}
> {"cores" : ">2", "node":"#ANY" , "strict" : false }
> {"freedisk" : "<10", "node":"#ANY" , "strict": false}
> {code}
> Solr would go through all these rules to identify if it breaks any such
> rules. If yes, it would go through the following steps
> # Identify all violations to such rules
> # Sort all nodes and identify the least loaded nodes
> # If there is an empty node
> ## store that node name
> ## Simulate removal of that node and go to step #1
> # Check if they are violating these rules
> # if yes, simulate moving them to other nodes with more load
> # if it is possible, to move without breaking rules,
> ## store that suggestion
> ## Go to step #1
> # If not possible, get the list of move operations (step #6.1) and collect
> the list of nodes to be removed ( step # 3.1)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
