[
https://issues.apache.org/jira/browse/TUBEMQ-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated TUBEMQ-265:
----------------------------------
Labels: pull-request-available (was: )
> Unexpected broker disappearance in broker list after updating default broker
> metadata
> -------------------------------------------------------------------------------------
>
> Key: TUBEMQ-265
> URL: https://issues.apache.org/jira/browse/TUBEMQ-265
> Project: Apache TubeMQ
> Issue Type: Bug
> Components: Broker, Master
> Reporter: Jeff Zhou
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's a bug on 0.5.0 after migration of
> [TUBEMQ-126|https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-126]:
> broker would disappear after updating its default metadata on
> unflushDataHold, which resulting an "out-of-sync" issue on metadata
> management.
> Reproduce steps:
> # Bring a broker online;
> # Use webapi to submit an update about type of
> "admin_update_broker_configure", setting a new unflushDataHold;
> # Monitor log, it would successfully fire this event and proceed the update;
> # Refresh the broker list on master, you will find it's disappeared;
> # Retry to add the broker with the same BrokerID and IP Address, it would
> raise an error about duplicated configuration found, but the broker is still
> unseen in the broker list.
> Bug is relating to BDB and Master initialization and meta-replication
> routines.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
