You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/20 04:39:27 UTC
[jira] [Commented] (APEXCORE-608) Streaming Containers use stale
RPC proxy after connection is closed
[ https://issues.apache.org/jira/browse/APEXCORE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831181#comment-15831181 ]
ASF GitHub Bot commented on APEXCORE-608:
-----------------------------------------
GitHub user vrozov opened a pull request:
https://github.com/apache/apex-core/pull/448
APEXCORE-608 Streaming Containers use stale RPC proxy after connection is closed
@tweise Please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/apex-core APEXCORE-608
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/448.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #448
----
commit cb471994898abb483656853e86d6512e9e4c10e4
Author: Vlad Rozov <v....@datatorrent.com>
Date: 2017-01-20T01:55:28Z
APEXCORE-608 Streaming Containers use stale RPC proxy after connection is closed
----
> Streaming Containers use stale RPC proxy after connection is closed
> -------------------------------------------------------------------
>
> Key: APEXCORE-608
> URL: https://issues.apache.org/jira/browse/APEXCORE-608
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Vlad Rozov
> Assignee: Vlad Rozov
>
> When Application is killed and Application Master is terminated, Streaming Containers initiate container exit sequence and use disconnected RPC proxy to report errors back to already terminated Application Master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)