[ https://issues.apache.org/jira/browse/SOLR-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043629#comment-15043629 ]
Erick Erickson edited comment on SOLR-8263 at 12/6/15 1:38 AM: --------------------------------------------------------------- The final patch for _just_ this JIRA to be applied after the trunk version after SOLR-6273. This patch supersedes all of the earlier 8263 patches This patch is included in the SOLR-6273-plus-8263-5x.patch. was (Author: erickerickson): The final patch for _just_ this JIRA to be applied after the trunk version of SOLR-6273 was applied. This patch is included in the SOLR-6273-plus-8263-5x.patch and supersedes all of the earlier 8263 patches > Tlog replication could interfere with the replay of buffered updates > -------------------------------------------------------------------- > > Key: SOLR-8263 > URL: https://issues.apache.org/jira/browse/SOLR-8263 > Project: Solr > Issue Type: Sub-task > Reporter: Renaud Delbru > Assignee: Erick Erickson > Fix For: 5.5, 6.0 > > Attachments: SOLR-6273-plus-8263-5x.patch, SOLR-8263-trunk-1.patch, > SOLR-8263-trunk-2.patch, SOLR-8263-trunk-3.patch, SOLR-8263.patch > > > The current implementation of the tlog replication might interfere with the > replay of the buffered updates. The current tlog replication works as follow: > 1) Fetch the the tlog files from the master > 2) reset the update log before switching the tlog directory > 3) switch the tlog directory and re-initialise the update log with the new > directory. > Currently there is no logic to keep "buffered updates" while resetting and > reinitializing the update log. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org