[jira] [Work logged] (ARTEMIS-2618) Improve Handling of Shutdown on critical I/O Error

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2618?focusedWorklogId=665596&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-665596 ]

ASF GitHub Bot logged work on ARTEMIS-2618:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Oct/21 10:01
            Start Date: 14/Oct/21 10:01
    Worklog Time Spent: 10m 
      Work Description: MrEasy opened a new pull request #3795:
URL: https://github.com/apache/activemq-artemis/pull/3795


   This can be used if running in environments where external applications temporarily lock journal files (e.g. virus scanners).
   Disabled by default.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 665596)
    Remaining Estimate: 0h
            Time Spent: 10m

> Improve Handling of Shutdown on critical I/O Error
> --------------------------------------------------
>
>                 Key: ARTEMIS-2618
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2618
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.11.0
>            Reporter: Rico Neubauer
>            Priority: Major
>             Fix For: 2.20.0
>
>         Attachments: Improve-Handling-of-Shutdown-on-critic.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Would like to request an improvement in the handling of critical I/O errors on opening journal files.
> If {{org.apache.activemq.artemis.core.io.nio.NIOSequentialFile}} fails to open a journal file, the whole server shuts down with {{@Message(id = 222010, value = "Critical IO Error, shutting down the server. file=1, message=0"}}.
> We have seen this in the wild, where a backup-software locked the file for a short time while journal was about getting opened, resulting in the shutdown.
> Proposed improvement would be to have a short-running retry for opening the journal files and only fail fatally if error persists.
> Will attach a proposal patch. Can also create a PR if you accept.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)