[
https://issues.apache.org/jira/browse/ARTEMIS-3402?focusedWorklogId=628833&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-628833
]
ASF GitHub Bot logged work on ARTEMIS-3402:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jul/21 02:23
Start Date: 28/Jul/21 02:23
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #3672:
URL: https://github.com/apache/activemq-artemis/pull/3672#issuecomment-887959656
I don't remember the exact conditions I have seen on DNSSwitchTest. That was
to fix the condition bought by the split brain.
I would have to debug again to give you some understanding. You could add
some log.debug into that and view the information there.
as I said I'm happy with this if tests are good. Make sure you run
DNSSwitchTest a couple of times manually on your laptop please.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 628833)
Time Spent: 1h 50m (was: 1h 40m)
> Split Brain detection should reject bad member updates
> ------------------------------------------------------
>
> Key: ARTEMIS-3402
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3402
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> During a split brain simulation with a single pair, the survived live can end
> up receiving a member update from the previous live (paused/unpaused) that's
> going to set the new live both as live and backup: split brain detection
> should fix the whole member update by rejecting it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
