You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Sami Siren (Created) (JIRA)" <ji...@apache.org> on 2012/01/27 18:46:27 UTC
[jira] [Created] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Let overseer process cluster state changes asynchronously
---------------------------------------------------------
Key: SOLR-3065
URL: https://issues.apache.org/jira/browse/SOLR-3065
Project: Solr
Issue Type: Improvement
Components: SolrCloud
Affects Versions: 4.0
Reporter: Sami Siren
Priority: Minor
Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Posted by "Mark Miller (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-3065.
-------------------------------
Resolution: Fixed
> Let overseer process cluster state changes asynchronously
> ---------------------------------------------------------
>
> Key: SOLR-3065
> URL: https://issues.apache.org/jira/browse/SOLR-3065
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3065.patch
>
>
> Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
> It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Posted by "Sami Siren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195705#comment-13195705 ]
Sami Siren commented on SOLR-3065:
----------------------------------
bq. we might want to at least log warnings on the '// XXX stop processing, exit' spots, at least for debugging purposes - I have not for the moment
sure. that's a good idea.
> Let overseer process cluster state changes asynchronously
> ---------------------------------------------------------
>
> Key: SOLR-3065
> URL: https://issues.apache.org/jira/browse/SOLR-3065
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3065.patch
>
>
> Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
> It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Posted by "Mark Miller (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195673#comment-13195673 ]
Mark Miller commented on SOLR-3065:
-----------------------------------
Thanks Sami - committing this now. Only comment is that we might want to at least log warnings on the '// XXX stop processing, exit' spots, at least for debugging purposes - I have not for the moment, but if you agree I will add them.
> Let overseer process cluster state changes asynchronously
> ---------------------------------------------------------
>
> Key: SOLR-3065
> URL: https://issues.apache.org/jira/browse/SOLR-3065
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3065.patch
>
>
> Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
> It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Assigned] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Posted by "Mark Miller (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller reassigned SOLR-3065:
---------------------------------
Assignee: Mark Miller
> Let overseer process cluster state changes asynchronously
> ---------------------------------------------------------
>
> Key: SOLR-3065
> URL: https://issues.apache.org/jira/browse/SOLR-3065
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3065.patch
>
>
> Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
> It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Posted by "Mark Miller (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3065:
------------------------------
Fix Version/s: 4.0
> Let overseer process cluster state changes asynchronously
> ---------------------------------------------------------
>
> Key: SOLR-3065
> URL: https://issues.apache.org/jira/browse/SOLR-3065
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3065.patch
>
>
> Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
> It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Posted by "Sami Siren (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sami Siren updated SOLR-3065:
-----------------------------
Attachment: SOLR-3065.patch
-process cluster state updates asynchronously (now once per 500ms)
-make sure overseer is still leader before updating the state
> Let overseer process cluster state changes asynchronously
> ---------------------------------------------------------
>
> Key: SOLR-3065
> URL: https://issues.apache.org/jira/browse/SOLR-3065
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Priority: Minor
> Attachments: SOLR-3065.patch
>
>
> Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
> It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3065) Let overseer process cluster state
changes asynchronously
Posted by "Sami Siren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195706#comment-13195706 ]
Sami Siren commented on SOLR-3065:
----------------------------------
bq. we might want to at least log warnings on the '// XXX stop processing, exit' spots, at least for debugging purposes - I have not for the moment
sure. that's a good idea.
> Let overseer process cluster state changes asynchronously
> ---------------------------------------------------------
>
> Key: SOLR-3065
> URL: https://issues.apache.org/jira/browse/SOLR-3065
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Sami Siren
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3065.patch
>
>
> Currently the overseer updates clusterstate.json on almost every change - one change at a time. This is not efficient when there are a lot of changes happening in short period of time (for example when a number of hosts are started at once).
> It would be better if changes were published on timely manner instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org