Also, please share any stack traces and things like that if possible.
Elasticsearch introduced some minor breaking changes to their APIs, and so
that would really help debug your situation.
On Thu, Aug 1, 2019 at 4:06 PM Mike Thomsen wrote:
> How big is the payload you are attempting to send to
How big is the payload you are attempting to send to Elasticsearch?
Thanks,
Mike
On Thu, Aug 1, 2019 at 9:52 AM Michal Tomaszewski
wrote:
> Hello,
>
>
>
> Please advice if there is any solution to use nifi with Elasticsearch 7.2?
>
> We need to use bulk load API PutElasticsearchHTTPrecord as w
Classification\_- INTERNAL & PARTNERS
Hello.
I still have some issues with the kerberized PutKudu on my 1.9.2 nifi cluster:
2019-08-01 16:15:28,207 DEBUG [Timer-Driven Process Thread-64]
o.a.n.security.krb.AbstractKerberosUser TGT was found, but has not reached
expiration window
2019-08-01 16:
Hello,
Please advice if there is any solution to use nifi with Elasticsearch 7.2?
We need to use bulk load API PutElasticsearchHTTPrecord as we load quite big
amount of data but after Elasticsearch upgrade to 7.x this component is not
loading any data and reporting timeouts.
Regards,
Giulia,
When you're experiencing this condition can you capture a thread dump and
share the logs (bootstrap/app)? To create this you can run
/bin/nifi.sh dump threaddump-locked-prov.log
Thanks
On Thu, Aug 1, 2019 at 3:57 AM Giulia Scalaberni <
giulia.scalabe...@genomedics.it> wrote:
> Hi,
>
>
Hi,
Both on my 1.9.2 and 1.9.0 standalone installations data provenance is
working correctly for nearly a month scheduled once a day then on the
server all the data provenance in all individual processors and in the
general reporting stays empty, even when I send new data through all the
processo
