[COMMUNITY MEETUP] June 10th at 10 AM PT

Hello everyone, This June 10th, at 10 AM PT we are hosting a new Data Lake Management community meetup, Introduction to Dataplex, an intelligent data fabric to power analytics at scale. Please register here https://www.crowdcast.io/e/9z2y62rz and join us! In this event, designed as a space for o

Re: Broken pipe write failed errors

We wanted to give you another data point. We tried 3.14.9 and 1.20 for the two libraries and no errors. Also, our services are http not https. Hope that helps. Thanks for mentioning the OkHttp client change. Any chance a future version of nifi could move back to the 3.x client series? On Tue,

Re: Broken pipe write failed errors

Robert, Thanks for the update, that's very interesting. Version 3.8.1 is several years old and is missing a number of updates related to HTTP/2 and TLS. OkHttp 3.12.0 introduced support for TLS 1.3 when running on a supported JVM, so if the connection is occurring over HTTPS, that may be part of

Re: Broken pipe write failed errors

David, Quick update for you. We decided after a bit of troubleshooting with zero luck to just downgrade the OKHttp to 3.8.1 and the okhttp-digest to 1.18, and no more errors. Not sure what to say. Robert On Mon, May 31, 2021 at 8:41 AM David Handermann wrote: > Hi Robert, > > Thanks for prov

RE: Failed to replicate request GET /nifi-api/flow/current-user

Hi Evgeniya, Thanks for your reply. We are setting our nifi cluster in a private Cloud with OpenSatck. All the instances (VMs) have internal IP like ‘192.168.x.x` and OpenStack manager what is called ‘floating IPs’ allowing to reach the VMs from outside the Cloud, sort of public IPs. So from ou

RE: Failed to replicate request GET /nifi-api/flow/current-user

Why did you set nifi.web.https.host to 0.0.0.0? I usually specify each node’s hostname/ip address in this parameter. Evgeniya Pankova Mob.: +7 (926) 327 44 05 | e-mail: ea.pank...@jet.su From: QUEVILLON EMMANUEL - EXT-SAFRAN ENGINEERING SERVICES (SAFRAN) Sent: Tuesday,

Failed to replicate request GET /nifi-api/flow/current-user

Dear list, I'm trying to set up a nifi cluster (3 nodes) secured with https. The cluster is able to start correctly, each node is able to communicate with each other, the primary/coordinator is well elected (reading the logs). I'm able to connect using my TLS certificates generated with tls-toolk