MINOR: Revert initial transactional state store semantics commit #19956
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #16922 and #18732 of incomplete feature.
PRs #16922 and #18732 are part of KIP-1035. In particular,
on starting a Kafka Streams instance, if it has pre-existing state, the
state stores are initialized on the main thread. Part of this
initialization registers the stateful metrics with the JMX thread-id tag
of
main
. This breaks the KIP-1076 implementation where need toregister metrics with thread-id tags of
xxxStreamThread-N
. This isnecessary due to the fact that the
StreamsMetric
is a singleton sharedby all
StreamThread
instances, so we need to make sure only addmetrics for the current
StreamThread
otherwise duplicate metrics areregistered. This PR reverts the changes until a fix is implemented,
allowing the individual
StreamThread
s to register the metrics.Reviewers: Matthias J. Sax matthias@confluent.io