Forgot this fun fact: while we're still on 1.14.0 on this particular NiFi
instance, it is a forked version which includes a cherry-pick of NIFI-9433.
So, it seems likely this is still a separate issue.
Again, we hope to reproduce in a test environment next week. An important
step is to determine
I'd like to get in on this one if you guys need anything.
On Fri, Jun 10, 2022 at 4:12 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Mike,
>
> Thanks for digging into this issue! I agree that simplifying the
> implementation makes going forward. The newer driver version involves
Mike,
Thanks for digging into this issue! I agree that simplifying the
implementation makes going forward. The newer driver version involves
changes in the Controller Service method signatures either way, so
streamlining the connection handling approach would be helpful.
Based on feedback,
https://issues.apache.org/jira/browse/NIFI-9770
Based on David's description saying it will require some deep changes
to how various properties are configured, I think this ticket would be
a good time to simplify the Cassandra bundle in general to just use a
controller service to configure the
Instead of creating an api/webhooks, you can just use a message queue
like Kafka, ActiveMQ, etc. Have NiFi subscribe to a queue and act on
inputs it gets from other systems. Does that answer your question?
On Thu, Jun 9, 2022 at 1:38 PM Shreyas Srinivasa
wrote:
>
> Hi,
>
> I am Shreyas working
Yes, it will be a few weeks at least to get the upgrade into the
environment where we see this occurring and eavluate. Part of the problem
is reproducibility. We haven't yet created a scenario that reliably forces
this situation. That's on the list for Monday though. If we can reliably
reproduce,
Mark
I will be a few weeks before you can evaluate this?
thanks
On Fri, Jun 10, 2022 at 11:03 AM Joe Witt wrote:
> MarkB
>
> That is why MarkP said it was a manifestation. Point is the issue you
> noted, specifically the behavior you saw here (and before) is believed to
> be addressed in
MarkB
That is why MarkP said it was a manifestation. Point is the issue you
noted, specifically the behavior you saw here (and before) is believed to
be addressed in that fix which went into the release 6 months ago and is
also in the 1.16.x line. You'll want that and of course the many other
This is not quite the same issue. It's possible the fix for NIFI-9433 may
be related. But, the set of circumstances are definitely different. Also,
the observed behavior is different. For example, none of the nodes report "
Cannot create negative queue size".
I'm trying to track specific
Mark,
This is a manifestation of NIFI-9433 [1] that we fixed a while back.
Recommend you upgrade your installation.
Thanks
-Mark
[1] https://issues.apache.org/jira/browse/NIFI-9433
On Jun 10, 2022, at 1:16 PM, Mark Bean
mailto:mark.o.b...@gmail.com>> wrote:
We have a situation where
We have a situation where several flowfiles have lost their content. They
still appear on the graph, but any attempt by a processor to access content
results in a NullPointerException. The identified content claim file is in
fact missing from the file system.
Also, there are ERROR log messages
11 matches
Mail list logo
