Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.8.0, 1.7.1
-
None
-
Ubuntu 18.4
Description
GetTCP does not reconnect when connection is broken.
Netstat reveals that the connection remains ESTABLISHED.
I understand that as GetTCP does not issue a heartbeat, GetTCP has no way on knowing that the connection has failed; as TCP does not know that the connection has failed. It is still ESTABLISHED.
Workaround:
Manually restating GetTCP processor when remote site is up fixes the connection.
Netstat reveals that FIN_WAIT1, then ESTABLISHED occurs, as expected.
Further Comments see:
- https://community.hortonworks.com/questions/222842/nifi-gettcp-140-problem-wont-reconnect.html
- https://community.hortonworks.com/questions/228934/gettcp-will-not-reconnect-nifi-180.html