[
https://issues.apache.org/jira/browse/IGNITE-19043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-19043:
-------------------------------------
Description:
After enabling ItRaftCommandLeftInLogUntilRestartTest failed with
{code:java}
org.opentest4j.AssertionFailedError: expected: not <null> {code}
while trying to retrieve previously added data after cluster restart. Seems
that it's because there's no corresponding data in PK index.
It is worth to mention that originally given test is about about raft log
re-application on node restart. So, I've commented all
partitionUpdateInhibitor in order to check whether it's related to
re-application or indexes themselves, problem is reproducible without
re-application logic.
It might be related to rocks to page memory defaults migration. Further
investigation required.
was:
After enabling ItRaftCommandLeftInLogUntilRestartTest failed with
{code:java}
org.opentest4j.AssertionFailedError: expected: not <null> {code}
while trying to retrieve previously added data after cluster restart. Seems
that it's because there's no corresponding data in PK index.
It is worth to mention that originally given test is about about raft log
re-application on node restart. So, I've commented all
partitionUpdateInhibitor in order to check whether it's related to
re-application or indexes themselves, problem is reproducible without
re-application logic.
It might be related to rocks to page memory defaults migration. Further
investigation required.
> ItRaftCommandLeftInLogUntilRestartTest: PageMemoryHashIndexStorage lacks data
> after cluster restart
> ---------------------------------------------------------------------------------------------------
>
> Key: IGNITE-19043
> URL: https://issues.apache.org/jira/browse/IGNITE-19043
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3
>
> After enabling ItRaftCommandLeftInLogUntilRestartTest failed with
> {code:java}
> org.opentest4j.AssertionFailedError: expected: not <null> {code}
> while trying to retrieve previously added data after cluster restart. Seems
> that it's because there's no corresponding data in PK index.
> It is worth to mention that originally given test is about about raft log
> re-application on node restart. So, I've commented all
> partitionUpdateInhibitor in order to check whether it's related to
> re-application or indexes themselves, problem is reproducible without
> re-application logic.
> It might be related to rocks to page memory defaults migration. Further
> investigation required.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
