UpdateConsensus could consume a lot of memory #1148
Assignees
Labels
kind/bug
This issue is a bug
Comments
yugabyte-ci
pushed a commit
that referenced
this issue
Apr 6, 2019
Summary: During some workload UpdateConsensus could take a long time to proceed, but leader keep trying to send new requests each 3 seconds. All those requests waiting on update_lock_ taking a lot of memory. Replaced std::mutex with std::timed_mutex and use RPC call timeout. So only 1-2 pending updates would wait and consume memory. Test Plan: ybd --gtest_filter QLStressTest.SlowUpdateConsensus Reviewers: mikhail, bogdan Reviewed By: bogdan Subscribers: ybase, bharat Differential Revision: https://phabricator.dev.yugabyte.com/D6444
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During some workload UpdateConsensus could take a long time to proceed, but leader keep trying to send new requests each 3 seconds. All those requests waiting on
update_lock_taking a lot of memory.The text was updated successfully, but these errors were encountered: