Thank you. Was able to get in.
Currently there are 1.8 million flow files and 3.2G. Is this too much
for a 3 node cluster with mutliple spindles each (SATA drives)?
Should I reduce the queue sizes?
-Joe
On 3/22/2023 10:23 AM, Phillip Lord wrote:
Joe,
If you need the UI to come back up, try setting the autoresume setting
in nifi.properties to false and restart node(s).
This will bring up every component/controllerService up
stopped/disabled and may provide some breathing room for the UI to
become available again.
Phil
On Mar 22, 2023 at 10:20 AM -0400, Joe Obernberger
<[email protected]>, wrote:
atop shows the disk as being all red with IO - 100% utilization. There
are a lot of flowfiles currently trying to run through, but I can't
monitor it because....UI wont' load.
-Joe
On 3/22/2023 10:16 AM, Mark Payne wrote:
Joe,
I’d recommend taking a look at garbage collection. It is far more
likely the culprit than disk I/O.
Thanks
-Mark
On Mar 22, 2023, at 10:12 AM, Joe Obernberger
<[email protected]> wrote:
I'm getting "java.net.SocketTimeoutException: timeout" from the
user interface of NiFi when load is heavy. This is 1.18.0 running
on a 3 node cluster. Disk IO is high and when that happens, I can't
get into the UI to stop any of the processors.
Any ideas?
I have put the flowfile repository and content repository on
different disks on the 3 nodes, but disk usage is still so high
that I can't get in.
Thank you!
-Joe
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
