On Fri, Dec 20, 2024 at 10:58 AM David Handermann
wrote:
>
> Nissim and Bryan,
>
> On closer evaluation, this appears to be a threading issue with the
> new StandardProxiedEntityEncoder and its use of
> CharsetEncoder.canEncode(). With CharsetEncoder being stateful, that
> explains why this can ha
Nissim and Bryan,
On closer evaluation, this appears to be a threading issue with the
new StandardProxiedEntityEncoder and its use of
CharsetEncoder.canEncode(). With CharsetEncoder being stateful, that
explains why this can happen intermittently.
I will cancel this release candidate build and pu
I just got the same error while on the primary/coordinator node,
investigating...
On Fri, Dec 20, 2024 at 10:34 AM David Handermann
wrote:
>
> Hi Nissim,
>
> Thanks for providing the stack trace. This stack trace seems to point
> to some other issue, as the failure itself relates to character set
Hi Nissim,
Thanks for providing the stack trace. This stack trace seems to point
to some other issue, as the failure itself relates to character set
parsing. It sounds like one node is returning some type of error
response from another node during the request replication process.
If you can look
Hello Team,
I am running into an issue when running on a three node cluster. If the ui is
brought up on one of the non-primary nodes, and refreshed, it give an error:
Invalid State
Current state = CODING_END, new state = CODING
I am interested if others see anything similar.
Code was compile
Team,
I am pleased to be calling this vote for the source release of Apache
NiFi 2.1.0.
Please review the following guide for how to verify a release candidate build:
https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
The source being voted on the and the convenienc
