ASF subversion and git services commented on ASTERIXDB-2188:

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

[ASTERIXDB-2188] Ensure recovery of component ids

- user model changes: no
- storage format changes: yes.
  Flush log record format changes.
- interface changes: no

- Add flush component ids to the flush log record. Upon
seeing a flush log record during recovery, schedule
a flush to all indexes in this partition s.t. LSN>maxDiskLSN
to ensure component ids are properly maintained upon
failed flushes.
- Add a test case to ensure the correctness of the recovery logic
of component ids

Change-Id: I8c1fc2b209cfb9d3dafa216771d2b7032eb99e75
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2408
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <bamou...@gmail.com>

> Ensure Component Ids Are Maintained During Recovery
> ---------------------------------------------------
>                 Key: ASTERIXDB-2188
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2188
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: STO - Storage
>            Reporter: Murtadha Hubail
>            Assignee: Chen Luo
>            Priority: Major
> We need to make sure that component ids are maintained if a failure happens 
> after a primary index's component is persisted to disk but before the 
> secondary indexes components are.

This message was sent by Atlassian JIRA

Reply via email to