Hello,
Is there any config which can be set to stop/kill the job manager if the client
has crashed due to some exception/error?
We see this in our application where client has crashed due to some issue like
making rest call or the application crash.
In such cases job manager continue to run ex
Hello,
Looking at existing restart strategies they are kind of generic. We have a
requirement to restart the job only in case of specific exception/issues.
What would be the best way to have a re start strategy which is based on few
rules like looking at particular type of exception or some extr
, 2017 at 2:26 PM, Ali, Kasif
mailto:kasif@gs.com>> wrote:
Hello,
We have added a serializer code which register all the schemas with
executionEnvironment and is called before execute(). This is to make sure that
all the avro schemas are pre-registered and cached in executors before
Hello,
We have added a serializer code which register all the schemas with
executionEnvironment and is called before execute(). This is to make sure that
all the avro schemas are pre-registered and cached in executors before actual
execution begin. Now while submitting the job we are getting