asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "abdullah alamoudi (Code Review)" <>
Subject Change in asterixdb[master]: Implemented Disk Components Alignment Based on IDs
Date Wed, 24 May 2017 04:44:24 GMT
abdullah alamoudi has posted comments on this change.

Change subject: Implemented Disk Components Alignment Based on IDs

Patch Set 6:

(1 comment)
File asterixdb/asterix-common/src/main/java/org/apache/asterix/common/context/

PS6, Line 103: isMergeLagging(
> Both solutions (with or without flow control) are solution OK to me. But wi
That should be fine because the merge policy should always checks the primary index disk components
on that partition.

What I am suggesting is only that when a secondary component is written to disk, the policy
should still check the primary. think of the following scenario:

You create 2 disk components each and you schedule a merge. the merge starts with the primary
index and finish while the secondaries are still being merged. then let's say 10 components
are added to each index. each time a component is added, it checks and sees that the secondaries
are still being merged, so it doesn't schedule any.

let's say at that point, data stops coming and all the secondaries are merged. the last secondary
to finish the merge should schedule the next set of merges. otherwise, the system will have
to wait until a new primary component is flushed.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I768ee9ac0a8d3c99c631086093a6b778b2e7588e
Gerrit-PatchSet: 6
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Luo Chen <>
Gerrit-Reviewer: Ian Maxon <>
Gerrit-Reviewer: Jenkins <>
Gerrit-Reviewer: Jianfeng Jia <>
Gerrit-Reviewer: Luo Chen <>
Gerrit-Reviewer: Till Westmann <>
Gerrit-Reviewer: Yingyi Bu <>
Gerrit-Reviewer: abdullah alamoudi <>
Gerrit-HasComments: Yes

View raw message