lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Talbot (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1170) Java replication replicates lucene lock file
Date Wed, 20 May 2009 05:52:45 GMT

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

Bryan Talbot commented on SOLR-1170:
------------------------------------

When the slave is cleanly shutdown, the lock file remains.  Doesn't that indicate an index
writer got left open and not properly shutdown?

> Java replication replicates lucene lock file
> --------------------------------------------
>
>                 Key: SOLR-1170
>                 URL: https://issues.apache.org/jira/browse/SOLR-1170
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 1.4
>         Environment: linux
>            Reporter: Bryan Talbot
>            Assignee: Noble Paul
>            Priority: Minor
>         Attachments: SOLR-1170.patch
>
>
> When using solr 1.4 replication, I see that the lucene-write.lock file is being replicated
to slaves.  I'm importing data from a db every 5 minutes using cron to trigger a DIH delta-import.
 Replication polls every 60 seconds and the master is configured to take a snapshot (replicateAfter)
commit.
> Why should the lock file be replicated to slaves?
> The lock file isn't stale on the master and is absent unless the delta-import is in process.
 I've not tried it yet, but with the lock file replicated, it seems like promotion of a slave
to a master in a failure recovery scenario requires the manual removal of the lock file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message