Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
MIME-Version: 1.0
In-Reply-To: <CAHvM9d0_mmH53+dgiQ2b5smRGsiPVdfayK0iEJKChb+b4_BxKw@mail.gmail.com>
References: <CAHvM9d0_mmH53+dgiQ2b5smRGsiPVdfayK0iEJKChb+b4_BxKw@mail.gmail.com>
From: Tushar Gosavi <tushar@datatorrent.com>
Date: Wed, 18 Jan 2017 11:55:22 +0530
Message-ID: <CAD0KA=PTJ_3b94Mw2Wfu=u77woo=O5Hzfokp8GjdAbhw8P1uag@mail.gmail.com>
Subject: Re: Shutdown of an Apex app
To: dev@apex.apache.org
Content-Type: text/plain; charset=UTF-8
archived-at: Wed, 18 Jan 2017 06:25:31 -0000

I think this would be a great addition for batch use cases or use
cases were DAG needs to be shutdown after detecting some
completion/error condition through the operator. We have one Jira
Opened for such functionality
https://issues.apache.org/jira/browse/APEXCORE-503.

- Tushar.


On Wed, Jan 18, 2017 at 11:45 AM, Bhupesh Chawda
<bhupesh@datatorrent.com> wrote:
> Hi All,
>
> Currently we can shutdown an Apex app in the following ways:
> 1. Throw ShutdownException() from *all* the input operators
> 2. Use Apex CLI to shutdown an app using the YARN App Id
>
> I think we should have some way of shutting down an application from within
> an operator. It is not always true that the trigger for shutdown is sent by
> the input operator only. Sometimes, an end condition may be detected by
> some operator in the DAG which wants the processing to end. Such a
> shutdown, although triggered from some intermediate operator in the DAG,
> should guarantee graceful shut down of the application.
>
> Thoughts?
>
> ~ Bhupesh