You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2021/06/03 07:17:00 UTC
[jira] [Updated] (IGNITE-14821) AssertionError: Historical iterator
tries to iterate WAL out of reservation
[ https://issues.apache.org/jira/browse/IGNITE-14821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladislav Pyatkov updated IGNITE-14821:
---------------------------------------
Description:
A reason of the issue is incorrect comparison WAL pointer, that leads to choose not quite the last pointer for reservation before rebalance. The old code selected the earliest WAL segment, but not the last pointer in it.
Assuming assertion error in description:
{code} Historical iterator tries to iterate WAL out of reservation [cache=SYSTEM_CACHEGROUP_LONGKEYS, reservedPointer=FileWALPointer [idx=10, fileOff=448674503, len=104925], historicalPointer=FileWALPointer [idx=10, fileOff=442844723, len=104925]] {code}
reservedPointer is chosen incorrect, but corresponds to the valid segment {{idx=10}} (the same as in historicalPointer).
A valid comparison of WAL pointers solved this issue. Segment number and segment offset participate in it together (look at the FileWalPointer#comapreTo method).
was:
A reason of the issue is incorrect comparison WAL pointer, that leads to choose not quite the last pointer for reservation before rebalance. The old code selected the earliest WAL segment, but not the last pointer in it.
Assuming assertion error in description:
Historical iterator tries to iterate WAL out of reservation [cache=SYSTEM_CACHEGROUP_LONGKEYS, reservedPointer=FileWALPointer [idx=10, fileOff=448674503, len=104925], historicalPointer=FileWALPointer [idx=10, fileOff=442844723, len=104925]]
reservedPointer is chosen incorrect, but corresponds to the valid segment {{idx=10}} (the same as in historicalPointer).
A valid comparison of WAL pointers solved this issue. Segment number and segment offset participate in it together (look at the FileWalPointer#comapreTo method).
> AssertionError: Historical iterator tries to iterate WAL out of reservation
> ---------------------------------------------------------------------------
>
> Key: IGNITE-14821
> URL: https://issues.apache.org/jira/browse/IGNITE-14821
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
>
> A reason of the issue is incorrect comparison WAL pointer, that leads to choose not quite the last pointer for reservation before rebalance. The old code selected the earliest WAL segment, but not the last pointer in it.
> Assuming assertion error in description:
> {code} Historical iterator tries to iterate WAL out of reservation [cache=SYSTEM_CACHEGROUP_LONGKEYS, reservedPointer=FileWALPointer [idx=10, fileOff=448674503, len=104925], historicalPointer=FileWALPointer [idx=10, fileOff=442844723, len=104925]] {code}
> reservedPointer is chosen incorrect, but corresponds to the valid segment {{idx=10}} (the same as in historicalPointer).
> A valid comparison of WAL pointers solved this issue. Segment number and segment offset participate in it together (look at the FileWalPointer#comapreTo method).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)