[
https://issues.apache.org/jira/browse/SOLR-16493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623691#comment-17623691
]
Jan Høydahl edited comment on SOLR-16493 at 10/25/22 9:07 AM:
--------------------------------------------------------------
My first suggestion [from this PR
comment|https://github.com/apache/solr/pull/1089#discussion_r1001629307] was
that Solr upon startup looks for a local file in a predefined location such as
{{$SOLR_HOME/bootstrap/clusterprops.json}} and if found, performs this logic:
# Validate the file, fail startup if malformed
# Check if {{/clusterprops.json}} exists in Zookeeper. If it does exist and is
non-empty, do nothing
# If {{/clusterprops.json}} does not exist in ZK or exists but empty ({{{}{
}{}}})
, upload the boostrap file
When a large cluster with many nodes, locking needs to allow exactly one node
to upload its bootstrap file.
NOTE: This simple mechanism should not be used for updating existing
clusterprops, only for setting the initial state on first bootstrap.
was (Author: janhoy):
My first suggestion [from this PR
comment|https://github.com/apache/solr/pull/1089#discussion_r1001629307] was
that Solr upon startup looks for a local file in a predefined location such as
{{$SOLR_HOME/bootstrap/clusterprops.json}} and if found, performs this logic:
# Validate the file, fail startup if malformed
# Check if {{/clusterprops.json}} exists in Zookeeper. If it does exist and is
non-empty, do nothing
# If {{/clusterprops.json}} does not exist in ZK or exists but empty
{{{}{}{}}}, upload the boostrap file
When a large cluster with many nodes, locking needs to allow exactly one node
to upload its bootstrap file.
NOTE: This simple mechanism should not be used for updating existing
clusterprops, only for setting the initial state on first bootstrap.
> A way to boostrap clusterprops statically on node startup
> ---------------------------------------------------------
>
> Key: SOLR-16493
> URL: https://issues.apache.org/jira/browse/SOLR-16493
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Priority: Major
>
> Today, boostrapping a cluster property needs minimum a running Zookeeper, or
> if you want to use Solr APIs, also a running Solr. This requires waiting for
> a healthy Solr instance, and posting a HTTP message with correct authz,
> checking for failures etc. This should be simpler, e.g. for use with Docker
> or for those who bundle Solr with another application.
> Common things you'd want to set is urlScheme and replica placement plugin.
> Use this Jira to discuss best way to solve this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
