You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/27 14:09:00 UTC
[jira] [Comment Edited] (IGNITE-11606) Index could not contain all
values from cache after index full rebuild
[ https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802830#comment-16802830 ]
Vladimir Ozerov edited comment on IGNITE-11606 at 3/27/19 2:08 PM:
-------------------------------------------------------------------
[~EdShangGG], I have a concern about changes in {{GridH2Table}}. We added {{Atomic.get()}} on a very hot path (update). While I do not expect any critical problems with it, but I'd prefer to use {{volatile + AtomicFieldUpdater}} instead. Looks good otherwise.
was (Author: vozerov):
[~EdShangGG], I have a concern about changes in {{GridH2Table}}. We added {{Atomic.get()}} on a very hot path (update). While I do not expect any critical problems with it, but I'd prefer to use {{volatile + AtomicFieldUpdater}} instead.
> Index could not contain all values from cache after index full rebuild
> ----------------------------------------------------------------------
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
> Reporter: Eduard Shangareev
> Assignee: Eduard Shangareev
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)