Hi Rob, Why do you say steaming is single threaded? I see a lot of background streaming threads running, for example:
"STREAM-IN-/10.210.165.49" daemon prio=10 tid=0x00007f81fc001000 nid=0x107075 runnable [0x00007f836b256000] "STREAM-IN-/10.213.51.57" daemon prio=10 tid=0x00007f81f0002000 nid=0x107073 runnable [0x00007f836b1d4000] "STREAM-IN-/10.213.51.61" daemon prio=10 tid=0x00007f81e8001000 nid=0x107070 runnable [0x00007f836b110000] "STREAM-IN-/10.213.51.63" daemon prio=10 tid=0x00007f81dc001800 nid=0x10706f runnable [0x00007f836b0cf000] Thanks Dikang. On Mon, Apr 20, 2015 at 6:48 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Mon, Apr 20, 2015 at 6:08 PM, Dikang Gu <dikan...@gmail.com> wrote: > >> When I bring in a new node into the cluster, it introduces significant >> load to the cluster. For the new node, the cpu usage is 100%, but disk >> write io is only around 50MB/s, while we have 10G network. >> >> Does it sound normal to you? >> > > Have you unthrottled both compaction and streaming via JMX/nodetool? > > Streaming is single threaded and can (?) be CPU bound, I would not be > surprised if JIRA contains a ticket on the upper bounds of streaming > performance in current implementation. > > =Rob > > > > -- Dikang
