You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Vitaliy Zhovtyuk (JIRA)" <ji...@apache.org> on 2014/11/08 21:37:33 UTC
[jira] [Commented] (SOLR-6054) Log progress of transaction log
replays
[ https://issues.apache.org/jira/browse/SOLR-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203587#comment-14203587 ]
Vitaliy Zhovtyuk commented on SOLR-6054:
----------------------------------------
i think this is enough to have state logging every one minute of replay, polling thread can lead to thread leaks issues.
SOLR-6403 does it well. SOLR-6054 can be closed as duplicate.
> Log progress of transaction log replays
> ---------------------------------------
>
> Key: SOLR-6054
> URL: https://issues.apache.org/jira/browse/SOLR-6054
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.9, Trunk
>
> Attachments: SOLR-6054.patch
>
>
> There is zero logging of how a transaction log replay is progressing. We should add some simple checkpoint based progress information. Logging the size of the log file at the beginning would also be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org