Matt Pavlovich

ref: https://issues.apache.org/jira/browse/AMQ-8463 I'd like to review the naming here, given the plans to add additional metrics. We should have it all align. Metrics: ``` nextMessageEnqueuedTimestamp (from the message’s brokerInTime) nextMessageTimestamp...

I don't think we should just 'drop' masterslave. It will break compatibility for other users. Can you please create a JIRA to discuss? I think we should: 1. Add a...

@lucastetreault at the very least, it would help to have unit tests showing the old name still works, vs refactoring that test. .. also the logger gets renamed. I think...

@lucastetreault thanks for updating to include deprecated for masterslave. In terms of naming-- I think "ha://" is more accurate (and shorter too!). 'leaderfollower' is not great here, since there is...

+1 'staticfailover' makes sense as the uri prefix.

@hboutemy what is the problem you are experiencing w/ builds not being reproducible?

@maxfortun the PR makes references to the now removed leveldb. Can you rebase and squash? To be clear-- this provides a job store only. KahaDB (or other persistence store) would...

Please hold on merge, need to review the terminology.

@cshannon yep. Plan to. I kicked in these PR’s to get the tests running in parallel to see fallout. I’ll be going through the unit test failures and adding the...

Note-- first test run failed on a StompTransport test (appears unrelated). Kicking off fresh run of tests