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

Memory usage grows steadily when running CassandraSecondaryIndex workload #346

Closed
robertpang opened this issue Jun 27, 2018 · 1 comment
Closed
Assignees
Labels
kind/bug This issue is a bug

Comments

@robertpang
Copy link
Contributor

When running the CassandraSecondaryIndex workload in a local RF3 cluster on Mac, the root memory tracker shows the memory is growing steadily and hitting the soft limit close to 1GB after about 2 mins:

$ java -jar ~/code/yugabyte/java/yb-loadtester/target/yb-sample-apps.jar \
  -workload CassandraSecondaryIndex -num_threads_read 0 -num_threads_write 4 \
  -nodes 127.0.0.1:9042
@robertpang robertpang added the kind/bug This issue is a bug label Jun 27, 2018
yugabyte-ci pushed a commit that referenced this issue Jul 5, 2018
Summary:
Added cleanup of committed transaction in TransactionParticipant.

We don't remove transaction when there are running requests, that reads provisional DB and could request status of this transaction.
So we store transaction in queue and wait when all requests that we launched before our try to remove this transaction are completed.
Since we try to remove transaction after all its records is removed from provisional DB it is safe to complete removal at this point, because it means that there will be no more queries to status of this transactions.

Test Plan: Jenkins

Reviewers: robert, mikhail

Reviewed By: mikhail

Subscribers: kannan, ybase

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

Fixed in commit fc6e50b.

jasonyb pushed a commit that referenced this issue Jun 11, 2024
PG-310: pg_stat_monitor: Bucket is Done vs still being current/last
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue is a bug
Projects
None yet
Development

No branches or pull requests

2 participants