This is an automated email from the ASF dual-hosted git repository.
jxue pushed a change to branch replica_level_throttle
in repository https://gitbox.apache.org/repos/asf/helix.git.
discard 29aaf64 Change throttling logic to per message (#1714)
omit ec00381 [Replica Level Throttle] Add per replica rebalance type
compute logic (#1703)
add 541d093 Fix test TestResourceChangeDetector. (#1712)
add 07e3ed5 Remove lock in HelixStateTransitionHandler (#1681)
add af3ee1c Change MessageQueueMonitor from static to dynamic metric
(#1715)
new b9e6f63 [Replica Level Throttle] Add per replica rebalance type
compute logic (#1703)
new 6fb8088 Change throttling logic to per message (#1714)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (29aaf64)
\
N -- N -- N refs/heads/replica_level_throttle (6fb8088)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../handling/HelixStateTransitionHandler.java | 96 +++++++++++-----------
.../monitoring/mbeans/MessageQueueMonitor.java | 63 ++++++--------
.../mbeans/MessageQueueMonitorMBean.java | 30 -------
.../changedetector/TestResourceChangeDetector.java | 93 ++++++++-------------
4 files changed, 109 insertions(+), 173 deletions(-)
delete mode 100644
helix-core/src/main/java/org/apache/helix/monitoring/mbeans/MessageQueueMonitorMBean.java
