tree c0f43d23c4b354f8ab18ceb6d02d9f6207eb066c
parent 3a6846942cde2f6e97ab53e01e14a7025ca04814
author Murtadha Hubail <mhubail@apache.org> 1535979202 +0300
committer Murtadha Hubail <mhubail@apache.org> 1536065959 -0700

[NO ISSUE][NET] Ensure CLOSE Is Not Sent After Channel ERROR

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- Currently it is possible to send network channel
  CLOSE command after a channel ERROR was sent. When this
  happens and the channel was recycled to be reused
  on the receiver side, the CLOSE command will result
  in NPE. There is no need to send a CLOSE command
  after an ERROR command because when an ERROR command
  is received, it is treated as ERROR + CLOSE on the
  receiver side.
- Avoid registering partition requests for failed jobs.

Change-Id: I17a769a46f4d13220adb22dd255e56dc4ccc458d
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2954
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Murtadha Hubail <mhubail@apache.org>
Reviewed-by: Michael Blow <mblow@apache.org>