[jira] [Commented] (SOLR-14289) Solr may attempt to check Chroot after already having connected once

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/SOLR-14289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241013#comment-17241013
 ] 

ASF subversion and git services commented on SOLR-14289:


Commit d4ea99f32690929ba9b4f81ee8d25107fda0e045 in lucene-solr's branch 
refs/heads/branch_8x from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=d4ea99f ]

SOLR-14958: Refactor zkHost config logic to make testing easier and reduce risk 
of incorrect value being used

(cherry picked from commit 37a61635e1c348bcdad9f73eea212b20305115c1)

Cherry pick was modified to resolve conflicts due to SOLR-14289 only existing 
on master.


> 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
>  Components: Server
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Major
> Fix For: master (9.0)
>
> Attachments: Screen Shot 2020-02-26 at 2.56.14 PM.png
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

[jira] [Commented] (SOLR-14289) Solr may attempt to check Chroot after already having connected once

[Mike Drob (Jira)]

[ 
https://issues.apache.org/jira/browse/SOLR-14289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053561#comment-17053561
 ] 

Mike Drob commented on SOLR-14289:
--

[~dsmiley] - seems like we're working on similar problems around speeding up 
core startup - can you take a look at this and let me know what you think?

> 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
>Priority: Major
> Attachments: Screen Shot 2020-02-26 at 2.56.14 PM.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org