mqadmin commands misorder large counters and timestamps

[yuluo-yx]

Description

Several mqadmin comparators subtract long values and cast the result to int. Consumer lag, tag counts, and message store timestamps can therefore be ordered incorrectly once their difference exceeds the int range.

Affected commands include consumerProgress, printMessageByQueue, and queryMsgByUniqueKey.

Expected behavior

Use overflow-safe long comparison so command output remains correctly ordered for large values.

[RockteMQ-AI]

Issue Evaluation

Category: type/bug | Status: Confirmed

The issue is valid. Multiple mqadmin commands use (int)(a - b) comparators for long values (consumer lag, tag counts, store timestamps). When the difference exceeds Integer.MAX_VALUE, ordering is reversed.

Root Cause: Subtraction-based Comparator narrowing long difference to int in consumerProgress, printMessageByQueue, and queryMsgByUniqueKey.
Impact: Admin tools — output ordering is incorrect for large values, misleading operators.
Severity: low-medium

Recommended fix: Replace all affected comparators with Long.compare(a, b).

An automated fix proposal can be generated. Reply /approve to proceed with PR generation.

---

Automated evaluation by RockteMQ-AI