[
https://issues.apache.org/jira/browse/NIFI-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509972#comment-17509972
]
Josef Zahner commented on NIFI-9820:
------------------------------------
Everything is better than the value today :).
Correct, an upgrade to a newer NiFi should not change the property or have an
impact for existing users. However this isn't the case anyway - right? Because
as soon as the processor is on the canvas, I would expect that the flow.xml.gz
file stores the value in any case. So an existing processor shouldn't be
impacted if NiFi changes the default
> Change PutKudu Property "Kudu Client Worker Count" Default Value
> ----------------------------------------------------------------
>
> Key: NIFI-9820
> URL: https://issues.apache.org/jira/browse/NIFI-9820
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.15.3
> Reporter: Josef Zahner
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The PutKudu processor property "Kudu Client Worker Count" has a suboptimal
> value. Please don't use the current "number of CPUs multiplied by 2"
> behaviour as it leads to a massive amount of workers in our case with
> physical servers. We have a 8-node cluster where each server has 64 CPUs. We
> have about 30 PutKudu processors configured -> a lot of worker threads per
> default just for kudu.
> We have changed the number of worker threads in our case to the number of
> concurrent tasks. I don't know, maybe it would be great to set it a bit
> higher than that, but to be honest, I don't exactly understand the impact. It
> looks still fast with the current config.
> *To sum it up, please set a low default value (eg. 4 or 8) for the property
> "Kudu Client Worker Count" and not a pseudo dynamic one for the PutKudu
> processor.*
> Btw. are there any suggestions how big the number should be?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
