# Tserver docker CPU load in idle

**URL:** https://forum.yugabyte.com/t/tserver-docker-cpu-load-in-idle/626
**Category:** General
**Created:** [February 8, 2020, 9:38pm UTC](https://forum.yugabyte.com/t/tserver-docker-cpu-load-in-idle/626 "2020-02-08T21:38:44Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![victor](https://avatars.discourse-cdn.com/v4/letter/v/3e96dc/32.png) [@victor](https://forum.yugabyte.com/u/victor)
#### Post date: [February 9, 2020, 6:45pm UTC](https://forum.yugabyte.com/t/tserver-docker-cpu-load-in-idle/626/3 "2020-02-09T18:45:22Z")

</div>

I use docker-compose to setup cluster in dev environment (win10 + docker) - docker has 8 cpus for all services. 6 empty tables (created on db updater start). Yes. Logs in attach for tserver1.

 ![Annotation 2020-02-09 204222](https://canada1.discourse-cdn.com/flex027/uploads/yugabyte/original/1X/12f44bc46623172719cf9e53733eb489b3c6f31e.jpeg)

Logs:

…

W0209 18:34:10.465245 19 reactor.cc:380] TabletServer\_R007: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 6 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:12.184116 13 reactor.cc:380] TabletServer\_R001: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 7 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:12.184180 15 reactor.cc:380] TabletServer\_R003: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 2 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:12.198673 17 reactor.cc:380] TabletServer\_R005: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 4 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:12.198679 14 reactor.cc:380] TabletServer\_R002: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 0 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:12.244817 141 replica\_state.cc:733] T e5645f251c394ca282b38125e1f10386 P 36f9a55694454f28941011b16cffc067 [term 3 LEADER]: Can’t advance the committed index across term boundaries until operations from the current term are replicated. Last committed operation was: { term: 1 index: 1 }, New majority replicated is: term: 1 index: 1, Current term is: 3  
W0209 18:34:13.625566 16 reactor.cc:380] TabletServer\_R004: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 2 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:13.625627 14 reactor.cc:380] TabletServer\_R002: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 1 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:23.969054 18 reactor.cc:380] TabletServer\_R006: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 4 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:23.969092 13 reactor.cc:380] TabletServer\_R001: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 0 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:23.983862 14 reactor.cc:380] TabletServer\_R002: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 1 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:23.983912 13 reactor.cc:380] TabletServer\_R001: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 7 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:24.004087 141 replica\_state.cc:733] T 435f874f25924e2e9055c968cac30dba P 36f9a55694454f28941011b16cffc067 [term 2 LEADER]: Can’t advance the committed index across term boundaries until operations from the current term are replicated. Last committed operation was: { term: 1 index: 1 }, New majority replicated is: term: 1 index: 1, Current term is: 2  
W0209 18:34:25.972113 14 reactor.cc:380] TabletServer\_R002: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 1 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:25.972182 15 reactor.cc:380] TabletServer\_R003: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 1 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:25.986752 15 reactor.cc:380] TabletServer\_R003: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 2 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:25.986797 19 reactor.cc:380] TabletServer\_R007: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 5 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:26.008317 140 replica\_state.cc:733] T 7dc71901204a459585ce9828ba10c0c3 P 36f9a55694454f28941011b16cffc067 [term 2 LEADER]: Can’t advance the committed index across term boundaries until operations from the current term are replicated. Last committed operation was: { term: 1 index: 1 }, New majority replicated is: term: 1 index: 1, Current term is: 2  
W0209 18:34:30.978746 13 reactor.cc:380] TabletServer\_R001: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 7 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:30.978780 12 reactor.cc:380] TabletServer\_R000: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 7 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:30.992595 17 reactor.cc:380] TabletServer\_R005: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 3 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:30.992645 14 reactor.cc:380] TabletServer\_R002: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 1 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:31.010702 140 replica\_state.cc:733] T 00f717bfad7847e7838bc59769cb0601 P 36f9a55694454f28941011b16cffc067 [term 2 LEADER]: Can’t advance the committed index across term boundaries until operations from the current term are replicated. Last committed operation was: { term: 1 index: 1 }, New majority replicated is: term: 1 index: 1, Current term is: 2  
W0209 18:34:31.980079 12 reactor.cc:380] TabletServer\_R000: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 6 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:31.980187 19 reactor.cc:380] TabletServer\_R007: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 6 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:31.994076 14 reactor.cc:380] TabletServer\_R002: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.10:9100 idx: 0 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:31.994104 14 reactor.cc:380] TabletServer\_R002: Client call yb.consensus.ConsensusService.RequestConsensusVote has no timeout set for connection id: { remote: 172.18.0.7:9100 idx: 1 protocol: 0x00007f927e0a8f00 → tcp }  
W0209 18:34:32.012917 140 replica\_state.cc:733] T 08584550feec4f70b729ebf72d0aca09 P 36f9a55694454f28941011b16cffc067 [term 2 LEADER]: Can’t advance the committed index across term boundaries until operations from the current term are replicated. Last committed operation was: { term: 1 index: 1 }, New majority replicated is: term: 1 index: 1, Current term is: 2

---

_[View the full topic](https://forum.yugabyte.com/t/tserver-docker-cpu-load-in-idle/626)._
