[
https://issues.apache.org/jira/browse/SOLR-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934004#comment-17934004
]
Gus Heck commented on SOLR-17694:
---------------------------------
{quote}I'm inclined to think Solr should reject such node names instead of
handle it gracefully. The work-around of avoiding such high server IDs seems
straight-forward.
{quote}
+1
> LeaderElector not able to parse node ID correctly when it has a leading dash
> ----------------------------------------------------------------------------
>
> Key: SOLR-17694
> URL: https://issues.apache.org/jira/browse/SOLR-17694
> Project: Solr
> Issue Type: Bug
> Reporter: Patrick
> Priority: Trivial
>
> This issue was
> [reported|https://lists.apache.org/thread/0pwxw1rzdffmbxctdzv2rmplzgwt6lpl]
> on [email protected].
> There could be time (e.g.: ZOOKEEPER-4904) when the node ID contains a
> leading dash
> {noformat}
> -5188057493699159958-1.1.1.15:8983_solr-n_0000192189
> {noformat}
> instead of just
> {noformat}
> 5188057493699159958-1.1.1.15:8983_solr-n_0000192189
> {noformat}
> In such case, LeaderElector.getNodeName returns
> *5188057493699159958-1.1.1.15:8983_solr* instead of just
> {*}1.1.1.15:8983_solr{*}.
> The problem is that the regex LeaderElector.NODE_NAME was not designed to
> handle the leading dash. LeaderElector.LEADER_SEQ and
> LeaderElector.SESSION_ID seem to have the same problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
