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

Metric for the number of transaction conflicts #277

Closed
mbautin opened this issue May 8, 2018 · 1 comment
Closed

Metric for the number of transaction conflicts #277

mbautin opened this issue May 8, 2018 · 1 comment
Assignees
Labels
kind/enhancement This is an enhancement of an existing feature

Comments

@mbautin
Copy link
Contributor

mbautin commented May 8, 2018

We need to measure the number of conflicts happening during distributed txn workloads.

@rao-vasireddy rao-vasireddy added the kind/enhancement This is an enhancement of an existing feature label May 8, 2018
yugabyte-ci pushed a commit that referenced this issue May 15, 2018
Summary: Add metric to measure distribute transaction conflicts. Also remove a debug check in YBTransaction::Impl::Abort.

Test Plan:
Run CassandraTransactionalKeyValue with small num_unique_keys relative to number of writers to force write conflicts and observe transaction_conflicts metric is incremented.

`java -jar ~/code/yugabyte/java/yb-loadtester/target/yb-sample-apps.jar -workload CassandraTransactionalKeyValue -num_threads_read 0 -num_threads_write 4 -nodes 127.0.0.1:9042 -num_unique_keys 8`

Reviewers: mikhail, sergei

Reviewed By: sergei

Subscribers: ybase

Differential Revision: https://phabricator.dev.yugabyte.com/D4816
@robertpang
Copy link
Contributor

Implemented in 62e9213.

jasonyb pushed a commit that referenced this issue Jul 10, 2024
v4.2.1 Fix bug in partition_data_time causing never-ending loop while…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement This is an enhancement of an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants