Check the resources on the host.
By default, the docker container will have all of the available memory on
the host machine available to it. If you'd like to ensure that this
available memory is at least X, you can use a memory reservation in your
docker compose file:
```
...
mem_reservation:
Can you put a forward proxy in front of the cluster and determine what
differs about the requests that result in a 400? Either this truly is the
client's fault, as the code suggests, or whatever oauth implementation
you're hitting is not a fan of issuing as many concurrent tokens as you
have nodes
It buys you what any API wrapper buys you: slightly increased developer
velocity at the expense of occasional bugs that aren't in your code. Are
you using python? Is your context that of a business that is attempting to
trade engineering spend for bottom-line beats (or bottom-line improvements
of
You're checking for `isNull`, but this value is not null, it is empty. Can
you add `isEmpty` as well before Multiplying? I also wonder if this value
is always a numeric string, rather than a number. If so, you'll also need
`toNumber`.
Try this, and consider adding toNumber if the field is
Hi Russ,
There is a default Java truststore located at
$JAVA_HOME/lib/security/cacerts that you should use.
Cannon
On Tue, Jul 26, 2022, 5:50 PM Russell Bateman wrote:
> I have hesitated between providing some huge tl;dr exposé and something
> shorter. I'll do shorter here.
>
> 0. For now,
Is it possible to achieve zero downtime rollouts for new nifi versions?
We have thus far been unsuccessful in convincing Nifi nodes to rejoin the
cluster after a version update. The exceptions being thrown range from
partial flow inheritance to missing nar bundles (we resolved this one).
Before
t rest in the configuration files.
>
> The properties in the flow.xml.gz file (e.g., your ConsumeMQTT processor
> password) are protected by a different mechanism, and there is not
> currently a Vault implementation that protects these.
>
> Hope this helps,
> Joe
>
> On Tue, Feb 1, 2022 at
Hello,
>From what I understand from the documentation, the transit engine of
Hashicorp Vault is definitely supported for system properties. It is also
clear that the standard key/value engine of Hashicorp vault is supported
for sensitive processor properties (e.g. the password used to connect to
