lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-7956) There are interrupts on shutdown in places that can cause ChannelAlreadyClosed exceptions which prevents proper closing of transaction logs.
Date Wed, 26 Aug 2015 18:47:46 GMT

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

Scott Blum commented on SOLR-7956:
----------------------------------

Interrupts permanently breaking index writers is our #1 production issue right now, so I've
just started looking at all the code and JIRAs related to this problem.  Glad I found this
one, I might try a backport to our ~5.2.1 instance.

One question, have you also audited the existing Future.cancel(true) calls?  I see several
of these in Solr.  The ones in ReplicationHandler and CommitTracker seem suspect to me, not
sure about HttpShardHandler (maybe that one doesn't hit any core stuff directly).

> There are interrupts on shutdown in places that can cause ChannelAlreadyClosed exceptions
which prevents proper closing of transaction logs.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7956
>                 URL: https://issues.apache.org/jira/browse/SOLR-7956
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: Trunk, 5.4
>
>         Attachments: SOLR-7956.patch
>
>
> Found this while beast testing HttpPartitionTest.



--
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


Mime
View raw message