You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a bug on 0.5.0 after migration of 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.
JIRA link - [INLONG-265] created by hystericalhell
The text was updated successfully, but these errors were encountered:
It's a bug on 0.5.0 after migration of TUBEMQ-126: broker would disappear after updating its default metadata on unflushDataHold, which resulting an "out-of-sync" issue on metadata management.
Reproduce steps:
Bug is relating to BDB and Master initialization and meta-replication routines.
JIRA link - [INLONG-265] created by hystericalhellThe text was updated successfully, but these errors were encountered: