dockerzhang opened a new issue #864: URL: https://github.com/apache/incubator-inlong/issues/864
<p>It's a bug on 0.5.0 after migration of <a href="https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-126"; class="external-link" rel="nofollow">TUBEMQ-126</a>: broker would disappear after updating its default metadata on unflushDataHold, which resulting an "out-of-sync" issue on metadata management.</p> <p>Reproduce steps:</p> <ol> <li>Bring a broker online;</li> <li>Use webapi to submit an update about type of "admin_update_broker_configure", setting a new unflushDataHold;</li> <li>Monitor log, it would successfully fire this event and proceed the update;</li> <li>Refresh the broker list on master, you will find it's disappeared;</li> <li>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.</li> </ol> <p>Bug is relating to BDB and Master initialization and meta-replication routines.</p> <i>JIRA link - <a href="https://issues.apache.org/jira/browse/INLONG-265";>[INLONG-265]</a> created by hystericalhell</i> -- 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]
