I’ve seen the same issue in 1.92 as well and opened the following ticket for it:
https://issues.apache.org/jira/browse/NIFI-6661<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.proofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fissues.apache.org-5Fjira-5Fbrowse-5FNIFI-2D2D6661-2526d-253DDwMGaQ-2526c-253DskUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w-2526r-253DWm89MSTpkAcFFP1M0uvGefI8slyO-5FVIaIza2IJwAlsU-2526m-253DFeafQec1Vx7cJvI-5FSg6wnvCs3r2AtNh80BPq-5Fa7kNQA-2526s-253DqRXhv1kd6YT6BhMH9xUQF6pnXxIKnhiOJehD-2DrjqY6c-2526e-253D-26data-3D02-257C01-257Cwilliam.gosse-2540aifoundry.com-257C84a5d6a52d9a498db26c08d738468778-257Cd29b7a9b6edb472099a83c5c6c3eeeb0-257C0-257C0-257C637039747880123423-26sdata-3DqB4M9PW2DXcimg6tFiWfcZu1UkOFfYjVfeqTU2nohj8-253D-26reserved-3D0&d=DwMGaQ&c=skUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w&r=Wm89MSTpkAcFFP1M0uvGefI8slyO_VIaIza2IJwAlsU&m=uqDl6yZLWnCOy1_ACkS9pwuOtoseL5_NvEKezbprzE8&s=y8jaWiHwvfCnrF17UQkQwVM2IBwkihI4LsHLdsTugvI&e=>

From: Wyllys Ingersoll <wyllys.ingers...@keepertech.com>
Sent: Friday, October 4, 2019 12:28 PM
To: users@nifi.apache.org
Subject: HandleHTTPRequest 503 error issue

[CAUTION: This email originated from outside of Kodak Alaris. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.]
________________________________

I believe this issue: 
https://issues.apache.org/jira/browse/NIFI-5522<https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_NIFI-2D5522&d=DwMFaQ&c=skUQKLuTFULvQUMqV0uyBaBvPxsA7Wk8MKjvMTLjY3w&r=Wm89MSTpkAcFFP1M0uvGefI8slyO_VIaIza2IJwAlsU&m=oHuMfLm2HO2_RNYYVPzWOz-GGx-uxCJDKcjjgpozVt8&s=eIrXJo7fyg4y1Qv6QC-vVyGBnesVYsh_A6cJkgHBWOo&e=>
  is a regression in Nifi 1.9.2, it was marked as fixed in 1.8.0, but Im seeing 
it a lot in 1.9.2

I can recreate it fairly regularly when I am hitting the endpoint pretty 
heavily and an error is encountered.  The process return 503 error (or nothing 
at all) and cannot be stopped or restarted without rebooting the entire node.

-Wyllys Ingersoll

Reply via email to