Does web ui hang for 1.4 for job submission ?

[Vishal Santoshi]

We have had 2 different installations and when e go submit a job, it gives us the spinning wheel and the request never reaches the JM. CLI works without issues. Is this us alone or some one else seen this. 

Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so we sure nothing should have changed on our side.

Apologies if this is a stupid question with an obvious solution.

Regards 

Vishal

[Ufuk Celebi]

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk


On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:

> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Vishal Santoshi]

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Vishal Santoshi]

The error is coming out as plain test with status 500.

On Wed, Jan 24, 2018 at 12:51 PM, Vishal Santoshi <[hidden email]> wrote:

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Lasse Nedergaard]

Hi. 

Our jobs take a number of command line options and validate them during startup and throw an exception if something is wrong. When this exception happens ui hang all prev. uploaded jars are removed most task manager are lost and all running jobs terminated. We running Flink 1.4 on dc/os

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 24. jan. 2018 kl. 18.51 skrev Vishal Santoshi <[hidden email]>:

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Vishal Santoshi]

Exactly, the same context and issue. We too depend on args too and server side  validations and that on error ui hangs.

On Wed, Jan 24, 2018 at 1:13 PM, Lasse Nedergaard <[hidden email]> wrote:

Hi. 

Our jobs take a number of command line options and validate them during startup and throw an exception if something is wrong. When this exception happens ui hang all prev. uploaded jars are removed most task manager are lost and all running jobs terminated. We running Flink 1.4 on dc/os

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 24. jan. 2018 kl. 18.51 skrev Vishal Santoshi <[hidden email]>:

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Chesnay Schepler]

In 1.4, jobs submitted through the WebUI that never actually execute a job will cause the UI to hang, with the only option
of resolving that being to reload the page.

This will be fixed for 1.4.1 and 1.5 .

On 24.01.2018 19:19, Vishal Santoshi wrote:

Exactly, the same context and issue. We too depend on args too and server side  validations and that on error ui hangs.

On Wed, Jan 24, 2018 at 1:13 PM, Lasse Nedergaard <[hidden email]> wrote:

Hi. 

Our jobs take a number of command line options and validate them during startup and throw an exception if something is wrong. When this exception happens ui hang all prev. uploaded jars are removed most task manager are lost and all running jobs terminated. We running Flink 1.4 on dc/os

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 24. jan. 2018 kl. 18.51 skrev Vishal Santoshi <[hidden email]>:

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Lasse Nedergaard]

Great news 👍

Does it also cover protection against loosing all your task managers?

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 25. jan. 2018 kl. 12.00 skrev Chesnay Schepler <[hidden email]>:

In 1.4, jobs submitted through the WebUI that never actually execute a job will cause the UI to hang, with the only option
of resolving that being to reload the page.

This will be fixed for 1.4.1 and 1.5 .

On 24.01.2018 19:19, Vishal Santoshi wrote:

Exactly, the same context and issue. We too depend on args too and server side  validations and that on error ui hangs.

On Wed, Jan 24, 2018 at 1:13 PM, Lasse Nedergaard <[hidden email]> wrote:

Hi. 

Our jobs take a number of command line options and validate them during startup and throw an exception if something is wrong. When this exception happens ui hang all prev. uploaded jars are removed most task manager are lost and all running jobs terminated. We running Flink 1.4 on dc/os

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 24. jan. 2018 kl. 18.51 skrev Vishal Santoshi <[hidden email]>:

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Chesnay Schepler]

That's a separate issue, and I would think deserves a JIRA as it sounds rather serious.

On 25.01.2018 12:43, Lasse Nedergaard wrote:

Great news 👍

Does it also cover protection against loosing all your task managers?

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 25. jan. 2018 kl. 12.00 skrev Chesnay Schepler <[hidden email]>:

In 1.4, jobs submitted through the WebUI that never actually execute a job will cause the UI to hang, with the only option
of resolving that being to reload the page.

This will be fixed for 1.4.1 and 1.5 .

On 24.01.2018 19:19, Vishal Santoshi wrote:

Exactly, the same context and issue. We too depend on args too and server side  validations and that on error ui hangs.

On Wed, Jan 24, 2018 at 1:13 PM, Lasse Nedergaard <[hidden email]> wrote:

Hi. 

Our jobs take a number of command line options and validate them during startup and throw an exception if something is wrong. When this exception happens ui hang all prev. uploaded jars are removed most task manager are lost and all running jobs terminated. We running Flink 1.4 on dc/os

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 24. jan. 2018 kl. 18.51 skrev Vishal Santoshi <[hidden email]>:

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal

[Vishal Santoshi]

In our case we do not see that happening...when the web ui hangs and we refresh the page it does not effect TMs etc.  Is there something splecific that you do that triggers this other issue ?

On Jan 25, 2018 7:15 AM, "Chesnay Schepler" <[hidden email]> wrote:

That's a separate issue, and I would think deserves a JIRA as it sounds rather serious.

On 25.01.2018 12:43, Lasse Nedergaard wrote:

Great news 👍

Does it also cover protection against loosing all your task managers?

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 25. jan. 2018 kl. 12.00 skrev Chesnay Schepler <[hidden email]>:

In 1.4, jobs submitted through the WebUI that never actually execute a job will cause the UI to hang, with the only option
of resolving that being to reload the page.

This will be fixed for 1.4.1 and 1.5 .

On 24.01.2018 19:19, Vishal Santoshi wrote:

Exactly, the same context and issue. We too depend on args too and server side  validations and that on error ui hangs.

On Wed, Jan 24, 2018 at 1:13 PM, Lasse Nedergaard <[hidden email]> wrote:

Hi. 

Our jobs take a number of command line options and validate them during startup and throw an exception if something is wrong. When this exception happens ui hang all prev. uploaded jars are removed most task manager are lost and all running jobs terminated. We running Flink 1.4 on dc/os

Med venlig hilsen / Best regards

Lasse Nedergaard

Den 24. jan. 2018 kl. 18.51 skrev Vishal Santoshi <[hidden email]>:

Yep, got it. It seems that the response when  in  an error state is reported by JM is not being rendered.

 We can see the response in the UI debugger but not on the UI itself.

On Wed, Jan 24, 2018 at 12:28 PM, Ufuk Celebi <[hidden email]> wrote:

It's not a stupid question at all! Try the following please:
1) Use something like Chrome's Developer Tools to check the responses
you get from the web UI. If you see an error there, that should point
you to what's going on.
2) Enable DEBUG logging for the JobManager and check the logs (if 1
doesn't help)

We just merged a change into master that does a better job of
reporting any errors that occur during submission.

– Ufuk

On Wed, Jan 24, 2018 at 5:24 PM, Vishal Santoshi
<[hidden email]> wrote:
> We have had 2 different installations and when e go submit a job, it gives
> us the spinning wheel and the request never reaches the JM. CLI works
> without issues. Is this us alone or some one else seen this.
>
> Again 1.3.2 does not have the issue and we have the same nodes, n/w etc so
> we sure nothing should have changed on our side.
>
> Apologies if this is a stupid question with an obvious solution.
>
> Regards
>
> Vishal