...also how does the heap and garbage collection look during this? On Sun, Jun 9, 2019, 5:58 PM Joe Witt <joe.w...@gmail.com> wrote:
> Joe > > When you view top or other tools what is dominating the cpu? > > thanks > joe > > On Sun, Jun 9, 2019, 5:35 PM Joe Gresock <jgres...@gmail.com> wrote: > >> I posted about this a while back on 1.6.0, but as far as I can tell it >> has only gotten worse in 1.9.2. >> >> I have a cluster of 7 nifi nodes running on CentOS 6 VMs. When no data >> is being processed, the UI console is very responsive. However, once I >> start processing lots of data, the CPU gets maxed by "user" processes and >> the console can no longer be used (either one or more node gets >> disconnected due to timeouts talking to the rest of the cluster, or the UI >> simply goes away). >> >> The impression I get is that threads are so prioritized for the processes >> that nothing can be spared for interacting with the console, or keeping the >> nodes connected to each other. >> >> Now, my latest idea would be to decrease the number of threads that my >> processors use, to try to give more CPU to the cluster overhead.. does this >> seem like a reasonable approach? >> >> A separate observation is that in 1.6.0, it usually took about a minute >> for all of the nodes to connect enough that the UI was available, starting >> from when the last node became officially "up". However, in 1.9.2, this >> takes about 15 minutes for the UI to become usable, during which time the >> UI claims no nodes are connected. >> >> I'm happy to provide thread dumps or other debugging output if anyone has >> an idea of how to improve this behavior. >> >> Thanks! >> Joe >> >> >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> >> Virus-free. >> www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> >> <#m_-4644020240664756686_m_-5737275650488698501_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >
