You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/01/10 22:09:00 UTC

[jira] [Commented] (ASTERIXDB-2234) Valid Components Should Be Determined by Index Checkpoint

    [ https://issues.apache.org/jira/browse/ASTERIXDB-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321205#comment-16321205 ] 

ASF subversion and git services commented on ASTERIXDB-2234:
------------------------------------------------------------

Commit 8769807ba9cd99af2d13c76b05fb328b4fe8ef27 in asterixdb's branch refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=8769807 ]

[ASTERIXDB-2234][STO] Delete Invalid Components

- user model changes: no
- storage format changes: no
- interface changes: yes
  - IIndexCheckpointManager:
    (+) getValidComponentTimestamp
    (+) getCheckpointCount
    (-) advanceLowWatermark

Details:
- Delete any component with start timestamp
  after the index checkpoint valid component
  timestamp on NC startup/shutdown.
- Add test case for deleting invalid components.

Change-Id: Ib11782edd79c7ef0c8949cb08e863b0ec1687a87
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2270
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mb...@apache.org>


> Valid Components Should Be Determined by Index Checkpoint
> ---------------------------------------------------------
>
>                 Key: ASTERIXDB-2234
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2234
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: STO - Storage
>            Reporter: Murtadha Hubail
>            Assignee: Murtadha Hubail
>
> Currently, valid disk component are determined by their validity bit. However, if a crash happens in the small window after the validity bit is set but before the index checkpoint is updated, the component shouldn't be considered valid. This can be avoided by cleaning any components that have greater timestamp than the checkpoint valid component timestamp on node startup. This will also give the advantage of cleaning any index invalid components without having to active the index.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)