shanthoosh merged pull request #953: Set job coordinator replication factor
configuration for standalone.
URL: https://github.com/apache/samza/pull/953
This is an automated message from the Apache Git Service.
To respond to
shanthoosh commented on issue #953: Set job coordinator replication factor
configuration for standalone.
URL: https://github.com/apache/samza/pull/953#issuecomment-473483420
@vjagadish1989
Can you take a look.
This is an
shanthoosh opened a new pull request #953: Set job coordinator replication
factor configuration for standalone.
URL: https://github.com/apache/samza/pull/953
This is an automated message from the Apache Git Service.
To
rmatharu opened a new pull request #952: Improved standby-aware container
allocation for active-containers on job redeploys
URL: https://github.com/apache/samza/pull/952
This is an automated message from the Apache Git
Hi Tom,
This would depend on what your k8s container orchestration logic looks
like. For example, in YARN, 'status' returns 'not running' after 'start'
until all the containers requested from the AM are 'running'. We also
leverage YARN to restart containers/job automatically on failures (within
+1 (Non-binding)
--
thanks
rayman
On Wed, Mar 13, 2019 at 7:17 PM Daniel Chen wrote:
> Hi,
>
> I performed the following verifications:
>
> 1. ./bin/check-all.sh succeeded.
>
> 2. Verified both ./bin/integration-tests.sh yarn-integration-tests and
> ./bin/integration-tests.sh
I'm using the LocalApplicationRunner and had added a liveness check
around the `status` method. The app is running in Kubernetes so, in
theory, it could be restarted if exceptions happened during processing.
However, it seems that "container failure" is divorced from "app
failure" because the app
