[ https://issues.apache.org/jira/browse/ASTERIXDB-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846010#comment-17846010 ]
ASF subversion and git services commented on ASTERIXDB-3394: ------------------------------------------------------------ Commit 9fdf5fdc217ae54508d1f64a6a7cb2c7cb26f4bb in asterixdb's branch refs/heads/master from Ritik Raj [ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=9fdf5fdc21 ] [ASTERIXDB-3394][STO] Introducing size bounded concurrent merge policy - user model changes: yes - storage format changes: no - interface changes: no Details: - Added storage property to set max mergable component size. - The new merge policy will schedule merges similar to the current ConcurrentMergePolicy but it will consider the max mergable component size. Change-Id: I0cf0cfcfe5e7ff0131430ce2039ba89929fda274 Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18264 Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Reviewed-by: Ritik Raj <raj.ritik9...@gmail.com> Reviewed-by: Wail Alkowaileet <wael....@gmail.com> > Introducing concurrent size bound merge policy > ---------------------------------------------- > > Key: ASTERIXDB-3394 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-3394 > Project: Apache AsterixDB > Issue Type: Improvement > Components: STO - Storage > Reporter: Ritik Raj > Priority: Major > Labels: triaged > > Introducing size-bound merge policy to account for cloud service providers' > max blob storage file size and to prevent exceeding that specified limit. > - Add storage config to set max mergable component size. > - Add a new merge policy and make it our default. > - The new merge policy will schedule merges similar to the current > ConcurrentMergePolicy but it will consider the max mergable component size. > - Update the isMergeLagging check on max components to use the "effective" > meragable components which can actually be merged rather than the current > total number of disk components. > - In case of max components is reached and no merges could be scheduled, > force a merge on the effective meragable components. -- This message was sent by Atlassian Jira (v8.20.10#820010)