You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Mike Drob (Jira)" <ji...@apache.org> on 2020/02/27 17:59:00 UTC
[jira] [Created] (SOLR-14289) Solr may attempt to check Chroot
after already having connected once
Mike Drob created SOLR-14289:
--------------------------------
Summary: Solr may attempt to check Chroot after already having connected once
Key: SOLR-14289
URL: https://issues.apache.org/jira/browse/SOLR-14289
Project: Solr
Issue Type: Task
Security Level: Public (Default Security Level. Issues are Public)
Components: Server
Reporter: Mike Drob
Assignee: Mike Drob
Attachments: Screen Shot 2020-02-26 at 2.56.14 PM.png
On server startup, we will attempt to load the solr.xml from zookeeper if we have the right properties set, and then later when starting up the core container will take time to verify (and create) the chroot even if it is the same string that we already used before. We can likely skip the second short-lived zookeeper connection to speed up our startup sequence a little bit.
See this attached image from thread profiling during startup.
!Screen Shot 2020-02-26 at 2.56.14 PM.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org