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
{{ message }}
This repository has been archived by the owner on Apr 1, 2024. It is now read-only.
As the multiple-snapshot introduced by PIP-196, the mechanism of Transaction Buffer Snapshot becomes more complex. We need more information to sense the status of the Transaction Buffer Snapshot.
Because the Transaction Buffer Snapshot is part of the Transaction Buffer, we plan to add an internal class in TransactionBufferStats to record the stats of the transaction snapshot.
Goal
Add an internal class in TransactionBufferStats to record the stats of the transaction snapshot. Let users can use the admin tool to get enough information about the transaction buffer snapshot.
API Changes
This PIP will change the result of admin.transactions().getTransactionBufferStats(yourTopicName);.
Implementation
The previous results are as follows:
publicclassTransactionBufferStats {
/** The state of this transaction buffer. */publicStringstate;
/** The max read position of this transaction buffer. */publicStringmaxReadPosition;
/** The last snapshot timestamps of this transaction buffer. */publiclonglastSnapshotTimestamps;
}
The expected results are as follows:
publicclassTransactionBufferStats {
/** The state of this transaction buffer. */publicStringstate;
/** The max read position of this transaction buffer. */publicStringmaxReadPosition;
/** The last snapshot timestamps of this transaction buffer.*/publiclonglastSnapshotTimestamps;
/** The stats of snapshots that only exist when enabling multiple snapshot segments. */publicSnapshotStatssnapshotStats;
publicstaticclassSnapshotStats {
publiclongsegmentsSize;
publiclongunsealedAbortTxnIDs;
}
}
Alternatives
No response
Anything else?
Compatibility
This modification will not break the previous usage of the admin tool.
In the previous usages, the snapshotStats will be ignored and other member variables have not changed.
In the new implementations, the users who enable the transaction buffer snapshot segment can get the snapshot segment stats from TransactionBufferStats.snapshotStats.
The text was updated successfully, but these errors were encountered:
Original Issue: apache#19628
Motivation
As the multiple-snapshot introduced by PIP-196, the mechanism of Transaction Buffer Snapshot becomes more complex. We need more information to sense the status of the Transaction Buffer Snapshot.
Because the Transaction Buffer Snapshot is part of the Transaction Buffer, we plan to add an internal class in
TransactionBufferStats
to record the stats of the transaction snapshot.Goal
Add an internal class in
TransactionBufferStats
to record the stats of the transaction snapshot. Let users can use the admin tool to get enough information about the transaction buffer snapshot.API Changes
This PIP will change the result of
admin.transactions().getTransactionBufferStats(yourTopicName);
.Implementation
Alternatives
No response
Anything else?
Compatibility
This modification will not break the previous usage of the admin tool.
In the previous usages, the
snapshotStats
will be ignored and other member variables have not changed.In the new implementations, the users who enable the transaction buffer snapshot segment can get the snapshot segment stats from
TransactionBufferStats.snapshotStats
.The text was updated successfully, but these errors were encountered: