[ https://issues.apache.org/jira/browse/ASTERIXDB-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131361#comment-16131361 ]
ASF subversion and git services commented on ASTERIXDB-2045: ------------------------------------------------------------ Commit fcd89f5a92a80b2b69d99845471856a5909be9a8 in asterixdb's branch refs/heads/master from [~mhubail] [ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=fcd89f5 ] [ASTERIXDB-2045][STO] Do Not Wait For Lagging Merge on Failed Flush - user model changes: no - storage format changes: no - interface changes: no Details: - Failed flush operations shouldn't wait for lagging merges since they won't add any new disk components. - Use logger to log exceptions. Change-Id: I915e993a76d5c692a276b1d7f3426a25f910cf46 Reviewed-on: https://asterix-gerrit.ics.uci.edu/1947 Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu> 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> > Failed flush shouldn't wait for lagging merge > --------------------------------------------- > > Key: ASTERIXDB-2045 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2045 > Project: Apache AsterixDB > Issue Type: Bug > Reporter: Murtadha Hubail > Assignee: Murtadha Hubail > > A failed flush shouldn't wait for lagging merge since it is not going to add > more disk components. -- This message was sent by Atlassian JIRA (v6.4.14#64029)