lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Updated] (SOLR-9278) Possible deadlock in replication
Date Thu, 29 Sep 2016 23:31:21 GMT


Mark Miller updated SOLR-9278:
    Affects Version/s:     (was: 6.1)
        Fix Version/s: 6.3

> Possible deadlock in replication
> --------------------------------
>                 Key: SOLR-9278
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Server
>    Affects Versions: 6.2
>         Environment: Linux
>            Reporter: Xunlong
>            Assignee: Mark Miller
>              Labels: replication
>             Fix For: 6.3, master (7.0)
>         Attachments: SOLR-9278.patch
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> There is a bug in IndexFetcher for replication logic, it may cause deadlock issue, and
it's very easy to reproduce. If you change your solrconfig to keep more than 1 commit points,
this operation will causes 2 issues:
> 1. Slave has to download whole index directory of Master, instead of incremental udpates
> 2. If you click "replicate now" button manually, this is cause deadlock, stop both "indexFetcher"
thread and "explicitFetcher" thread.
> The first issue is a design issue, can be worked around by keep only 1 commit point.
But the second issue can always happen if there is some file located in slave's index directory,
but can not be deleted by index delete policy (due to permission issue etc), I have fixed
this issue for my service, would happy to contribute to Solr community to benefit others.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message