[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13586729#comment-13586729 ] Commit Tag Bot commented on SOLR-4078: -- [branch_4x commit] Mark Robert Miller http://svn.apache.org/viewvc?view=revisionrevision=1450013 SOLR-4078: Allow custom naming of SolrCloud nodes so that a new host:port combination can take over for a previous shard. Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.2, 5.0 Attachments: SOLR-4078.patch, SOLR-4078.patch, SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13586730#comment-13586730 ] Commit Tag Bot commented on SOLR-4078: -- [trunk commit] Mark Robert Miller http://svn.apache.org/viewvc?view=revisionrevision=1450012 SOLR-4078: Allow custom naming of SolrCloud nodes so that a new host:port combination can take over for a previous shard. Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.2, 5.0 Attachments: SOLR-4078.patch, SOLR-4078.patch, SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13585664#comment-13585664 ] Mark Miller commented on SOLR-4078: --- I'm close with this - working on some final quirks and tests. Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.2, 5.0 Attachments: SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571543#comment-13571543 ] Michael Della Bitta commented on SOLR-4078: --- +1 definitely interested. Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.2, 5.0 Attachments: SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511230#comment-13511230 ] Po Rui commented on SOLR-4078: -- we interest in this feature. we look foreword this feature just in case ^_^ Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.1, 5.0 Attachments: SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511400#comment-13511400 ] Yonik Seeley commented on SOLR-4078: +1, this definitely seems like where we want to be going. Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.1, 5.0 Attachments: SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511070#comment-13511070 ] Mark Miller commented on SOLR-4078: --- Anyone interested in this feature? Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.1, 5.0 Attachments: SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4078) Allow custom naming of nodes so that a new host:port combination can take over for a previous shard.
[ https://issues.apache.org/jira/browse/SOLR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501376#comment-13501376 ] Mark Miller commented on SOLR-4078: --- note for me: not sure i caught this one in the patch final String key = coreState.getStr(ZkStateReader.NODE_NAME_PROP) + _ + coreState.getStr(ZkStateReader.CORE_NAME_PROP); Allow custom naming of nodes so that a new host:port combination can take over for a previous shard. Key: SOLR-4078 URL: https://issues.apache.org/jira/browse/SOLR-4078 Project: Solr Issue Type: New Feature Components: SolrCloud Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.1, 5.0 Attachments: SOLR-4078.patch Currently we auto assign a unique node name based on the host address and core name - we should let the user optionally override this so that a new host address + core name combo can take over the duties of a previous registered node. Especially useful for ec2 if you are not using elastic ips. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
