I'm running into an issue with replication caused by outdated SequenceIndex records. Drupal\replication\Changes\Changes::getNormal() will end up causing a fatal error when it can't load the revsion for a sequence.

I'm guessing the SequenceIndex records need to be removed. Is that safe? Are there any side-effects?

Any other ideas?

CommentFileSizeAuthor
#7 replication-ignore-filter-missing-record-2823882-7.patch426 bytesl0ke
#3 2823882-3.patch502 bytesJamesK

Comments

JamesK created an issue. See original summary.

JamesK’s picture

JamesK commented
Project: Multiversion » Replication
JamesK’s picture

JamesK commented
Title: How to remove SequenceIndex records for purged entities? » Ignore SequenceIndex records for missing entities
Assigned: Unassigned » JamesK
StatusFileSize
new 2823882-3.patch502 bytes

Here's a workaround.

JamesK’s picture

JamesK commented
Category: Support request » Bug report
Status: Active » Needs review
jeqq’s picture

jeqq commented
Status: Needs review » Needs work

@JamesK what is the error? If this is caused by a sequence of a "deleted" revision then of course it has side effects, it should return deleted changes too. I should see the error for a more accurate answer.

  • jeqq committed 72cba8a on 8.x-1.x 
    Revert "Issue #2823882 by JamesK, jeqq: Ignore SequenceIndex records for...
  • jeqq committed c57a4bf on 8.x-1.x authored by JamesK
    Issue #2823882 by JamesK, jeqq: Ignore SequenceIndex records for missing...
l0ke’s picture

l0ke
Primary language English
Location Ukraine
commented
Status: Needs work » Needs review
StatusFileSize
new replication-ignore-filter-missing-record-2823882-7.patch426 bytes

@jeqq It may work to just skip filter as you suggested.

  • jeqq committed 5676363 on 8.x-1.x authored by JamesK 
    Issue #2823882 by JamesK, l0ke, jeqq: Ignore SequenceIndex records for...
jeqq’s picture

jeqq commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.