[
https://issues.apache.org/jira/browse/ASTERIXDB-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17930588#comment-17930588
]
ASF subversion and git services commented on ASTERIXDB-3564:
------------------------------------------------------------
Commit af29cbe759a8e9a8b865cad70fac01737f6ceb5b in asterixdb's branch
refs/heads/master from Savyasach Reddy
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=af29cbe759 ]
[ASTERIXDB-3564][STO]: Avoid halts on IO operation failures
- user model changes: no
- storage format changes: no
- interface changes: yes
details:
- Retry Flush Operations on IOException
- Avoid Halts on Merge failure
- Make Create Index operation retryable
Ext-ref: MB-63040
Change-Id: If253ea03f5baecbab226e527abb4267670a4233e
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19187
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Ritik Raj <[email protected]>
Tested-by: Ritik Raj <[email protected]>
> Avoid halts on IO operation failures
> ------------------------------------
>
> Key: ASTERIXDB-3564
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3564
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: STO - Storage
> Reporter: Savyasach Reddy Enukonda
> Priority: Critical
> Labels: triaged
>
> Currently whenever a failure is encountered during a merge or a flush
> operation, that results in a JVM halt. We should avoid those halts, do the
> required cleanup, and retry the IO operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
