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

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

                Author: ASF GitHub Bot
            Created on: 10/Nov/22 18:09
            Start Date: 10/Nov/22 18:09
    Worklog Time Spent: 10m 
      Work Description: jbertram merged PR #4245:
URL: https://github.com/apache/activemq-artemis/pull/4245




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

    Worklog Id:     (was: 825030)
    Time Spent: 20m  (was: 10m)

> AMQ222010 (No such file or directory) during startup
> ----------------------------------------------------
>
>                 Key: ARTEMIS-4030
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4030
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.19.1, 2.26.0
>            Reporter: Nicolas Verducou
>            Assignee: Domenico Francesco Bruscino
>            Priority: Major
>         Attachments: qa1-mb.log
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Hello,
> We have a cluster of 2 nodes in shared storage mode. The shared storage is an 
> NFS.
> While restarting the master node (the backup was live and active), we 
> observed this exception:  
> AMQ222010: Critical IO Error, shutting down the server. 
> file=NIOSequentialFile 
> /remote/activemq-data/qa/mb_qa2/data_amq/paging/65638e0a-451b-11ed-8450-00505697747e/000000004.page,
>  
> message=/remote/activemq-data/qa/mb_qa2/data_amq/paging/65638e0a-451b-11ed-8450-00505697747e/000000004.page
>  (No such file or directory): ActiveMQIOErrorException[errorType=IO_ERROR 
> message=/remote/activemq-data/qa/mb_qa2/data_amq/paging/65638e0a-451b-11ed-8450-00505697747e/000000004.page
>  (No such file or directory)]
> Just after we can see
> AMQ221007: Server is now live 
> But at this stage the 2nd node remains the active one.
> After restarting the 2nd node, it became backup and not live so neither 1st 
> node nor 2nd node were accepting traffic
>  
> What could explain the I/O issue in the first place?
> How come we can get AMQ221007 just after AMQ222010?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to