lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Talbot (JIRA)" <>
Subject [jira] Commented: (SOLR-1170) Java replication replicates lucene lock file
Date Tue, 19 May 2009 15:50:46 GMT


Bryan Talbot commented on SOLR-1170:

The lock file doesn't show up in the filelist.  It always has the same timestamp as other
files which were replicated and sticks around until the next replication begins so I had assumed
it was replicated.

If it is created on the slave instead of being replicated, isn't that still an issue?  I'm
certain that there are no writes being performed on the slave.

> Java replication replicates lucene lock file
> --------------------------------------------
>                 Key: SOLR-1170
>                 URL:
>             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)
> 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.

View raw message