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:19:14 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(
> To avoid this isMergeLagging method, another way we could do is that when t
I am strongly opposed to delay of flushes for the sake of merges. Not sure what others think.
Here is how this could be done.

1. The merge policy should not schedule new merges if there is an ongoing merge for either
a primary or secondary index of the dataset on the partition.

2. merges could be triggered by a new disk component of the primary index or any secondary

There is a needed synchronization but that should be okay IMO. much better than slowing down
flushes and in turn data ingestion.

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