Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZOOKEEPER-4750: Align RequestPathMetricsCollector with FinalRequestProcessor and OpCode #2166

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kezhuw
Copy link
Member

@kezhuw kezhuw commented May 22, 2024

Currently, some path aware opcodes were not reported in FinalRequestProcessor
and some were not handled in RequestPathMetricsCollector. This commit aligns
them with ZooDefs.OpCode.

…ocessor and OpCode

Currently, some path aware opcodes were not reported in `FinalRequestProcessor`
and some were not handled in `RequestPathMetricsCollector`. This commit aligns
them with `ZooDefs.OpCode`.
@@ -140,6 +150,7 @@ static boolean isWriteOp(int requestType) {
case ZooDefs.OpCode.sync:
case ZooDefs.OpCode.create:
case ZooDefs.OpCode.create2:
case ZooDefs.OpCode.createTTL:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added only createTTL here.

  • addWatch touches no persistent data but only volatile data.
  • check itself modifies nothing. If data of the checking path is modified, it will be tracked through another opcode.
  • reconfig is here already.

Besides above, does sync considered as a write opcode ? I try to be conservative to changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant