[
https://issues.apache.org/jira/browse/SOLR-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566916#comment-16566916
]
Shawn Heisey commented on SOLR-12611:
-------------------------------------
The reason that the sleep was so short in my alternate code was because I
wanted to make sure that the loop can exit quickly when the run flag goes false.
My overall knowledge did not include information like daemon threads. After
looking that up, it sounds like a great idea, and simplifies the code. Thanks
for the info!
My motivation here is from the perspective of helping people with Solr
problems. I've seen situations where users do think of sending a stacktrace,
but do not mention which version of Solr they're running. Asking for missing
information can mean a long delay in figuring out the problem.
> Add version information to thread dump
> --------------------------------------
>
> Key: SOLR-12611
> URL: https://issues.apache.org/jira/browse/SOLR-12611
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.4
> Reporter: Shawn Heisey
> Priority: Trivial
> Attachments: SOLR-12611.patch
>
>
> Thread dumps contain stacktrace info. Without knowing the Solr version, it
> can be difficult to compare stacktraces to source code.
> If exact version information is available in the thread dump, it will be
> possible to look at source code to understand stacktrace information. If
> *full* version information is present, then it would even be possible to
> learn whether the user is running an official binary build or if they have
> built Solr themselves.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
