[jira] [Updated] (FLINK-31931) Exception history page should not link to a non-existent TM log page.

2023-08-11 Thread Flink Jira Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-31931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-31931:
---
Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> Exception history page should not link to a non-existent TM log page.
> -
>
> Key: FLINK-31931
> URL: https://issues.apache.org/jira/browse/FLINK-31931
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Web Frontend
>Reporter: Junrui Li
>Assignee: Junrui Li
>Priority: Major
>  Labels: pull-request-available, stale-assigned
>
> In FLINK-30358, we supported to show the task manager ID on the exception 
> history page and added a link to the task manager ID to jump to the task 
> manager page. However, if the task manager no longer exists when clicking the 
> link to jump, the page will continue to load and the following error log will 
> be continuously printed in the JM log. This will trouble users, and should be 
> optimized.
> {code:java}
> 2023-04-25 11:40:50,109 [flink-akka.actor.default-dispatcher-35] ERROR 
> org.apache.flink.runtime.rest.handler.taskmanager.TaskManagerDetailsHandler 
> [] - Unhandled exception.
> org.apache.flink.runtime.resourcemanager.exceptions.UnknownTaskExecutorException:
>  No TaskExecutor registered under container_01.
>   at 
> org.apache.flink.runtime.resourcemanager.ResourceManager.requestTaskManagerDetailsInfo(ResourceManager.java:697)
>  ~[flink-dist-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) ~[?:?]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_362]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_362]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.lambda$handleRpcInvocation$1(AkkaRpcActor.java:309)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:83)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcInvocation(AkkaRpcActor.java:307)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:222)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:84)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:168)
>  ~[?:?]
>   at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:24) ~[?:?]
>   at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:20) ~[?:?]
>   at scala.PartialFunction.applyOrElse(PartialFunction.scala:127) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction.applyOrElse$(PartialFunction.scala:126) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:20) 
> ~[?:?]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:175) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at akka.actor.Actor.aroundReceive(Actor.scala:537) ~[?:?]
>   at akka.actor.Actor.aroundReceive$(Actor.scala:535) ~[?:?]
>   at akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:220) ~[?:?]
>   at akka.actor.ActorCell.receiveMessage(ActorCell.scala:579) ~[?:?]
>   at akka.actor.ActorCell.invoke(ActorCell.scala:547) ~[?:?]
>   at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:270) ~[?:?]
>   at akka.dispatch.Mailbox.run(Mailbox.scala:231) ~[?:?]
>   at akka.dispatch.Mailbox.exec(Mailbox.scala:243) ~[?:?]
>   at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) 
> [?:1.8.0_362]
>   at 
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) 
> [?:1.8.0_362]
>   at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) 
> [?:1.8.0_362]
>   at 
> 

[jira] [Updated] (FLINK-31931) Exception history page should not link to a non-existent TM log page.

2023-05-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-31931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-31931:
---
Labels: pull-request-available  (was: )

> Exception history page should not link to a non-existent TM log page.
> -
>
> Key: FLINK-31931
> URL: https://issues.apache.org/jira/browse/FLINK-31931
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Web Frontend
>Reporter: Junrui Li
>Assignee: Junrui Li
>Priority: Major
>  Labels: pull-request-available
>
> In FLINK-30358, we supported to show the task manager ID on the exception 
> history page and added a link to the task manager ID to jump to the task 
> manager page. However, if the task manager no longer exists when clicking the 
> link to jump, the page will continue to load and the following error log will 
> be continuously printed in the JM log. This will trouble users, and should be 
> optimized.
> {code:java}
> 2023-04-25 11:40:50,109 [flink-akka.actor.default-dispatcher-35] ERROR 
> org.apache.flink.runtime.rest.handler.taskmanager.TaskManagerDetailsHandler 
> [] - Unhandled exception.
> org.apache.flink.runtime.resourcemanager.exceptions.UnknownTaskExecutorException:
>  No TaskExecutor registered under container_01.
>   at 
> org.apache.flink.runtime.resourcemanager.ResourceManager.requestTaskManagerDetailsInfo(ResourceManager.java:697)
>  ~[flink-dist-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) ~[?:?]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_362]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_362]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.lambda$handleRpcInvocation$1(AkkaRpcActor.java:309)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:83)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcInvocation(AkkaRpcActor.java:307)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:222)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:84)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:168)
>  ~[?:?]
>   at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:24) ~[?:?]
>   at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:20) ~[?:?]
>   at scala.PartialFunction.applyOrElse(PartialFunction.scala:127) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction.applyOrElse$(PartialFunction.scala:126) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:20) 
> ~[?:?]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:175) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at akka.actor.Actor.aroundReceive(Actor.scala:537) ~[?:?]
>   at akka.actor.Actor.aroundReceive$(Actor.scala:535) ~[?:?]
>   at akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:220) ~[?:?]
>   at akka.actor.ActorCell.receiveMessage(ActorCell.scala:579) ~[?:?]
>   at akka.actor.ActorCell.invoke(ActorCell.scala:547) ~[?:?]
>   at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:270) ~[?:?]
>   at akka.dispatch.Mailbox.run(Mailbox.scala:231) ~[?:?]
>   at akka.dispatch.Mailbox.exec(Mailbox.scala:243) ~[?:?]
>   at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) 
> [?:1.8.0_362]
>   at 
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) 
> [?:1.8.0_362]
>   at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) 
> [?:1.8.0_362]
>   at 
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175) 
> [?:1.8.0_362]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-31931) Exception history page should not link to a non-existent TM log page.

2023-04-25 Thread Martijn Visser (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-31931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martijn Visser updated FLINK-31931:
---
Fix Version/s: (was: 1.18.0)

> Exception history page should not link to a non-existent TM log page.
> -
>
> Key: FLINK-31931
> URL: https://issues.apache.org/jira/browse/FLINK-31931
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / Web Frontend
>Reporter: Junrui Li
>Assignee: Junrui Li
>Priority: Major
>
> In FLINK-30358, we supported to show the task manager ID on the exception 
> history page and added a link to the task manager ID to jump to the task 
> manager page. However, if the task manager no longer exists when clicking the 
> link to jump, the page will continue to load and the following error log will 
> be continuously printed in the JM log. This will trouble users, and should be 
> optimized.
> {code:java}
> 2023-04-25 11:40:50,109 [flink-akka.actor.default-dispatcher-35] ERROR 
> org.apache.flink.runtime.rest.handler.taskmanager.TaskManagerDetailsHandler 
> [] - Unhandled exception.
> org.apache.flink.runtime.resourcemanager.exceptions.UnknownTaskExecutorException:
>  No TaskExecutor registered under container_01.
>   at 
> org.apache.flink.runtime.resourcemanager.ResourceManager.requestTaskManagerDetailsInfo(ResourceManager.java:697)
>  ~[flink-dist-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) ~[?:?]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_362]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_362]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.lambda$handleRpcInvocation$1(AkkaRpcActor.java:309)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:83)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcInvocation(AkkaRpcActor.java:307)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:222)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:84)
>  ~[?:?]
>   at 
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:168)
>  ~[?:?]
>   at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:24) ~[?:?]
>   at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:20) ~[?:?]
>   at scala.PartialFunction.applyOrElse(PartialFunction.scala:127) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction.applyOrElse$(PartialFunction.scala:126) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:20) 
> ~[?:?]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:175) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:176) 
> ~[flink-scala_2.12-1.17-SNAPSHOT.jar:1.17-SNAPSHOT]
>   at akka.actor.Actor.aroundReceive(Actor.scala:537) ~[?:?]
>   at akka.actor.Actor.aroundReceive$(Actor.scala:535) ~[?:?]
>   at akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:220) ~[?:?]
>   at akka.actor.ActorCell.receiveMessage(ActorCell.scala:579) ~[?:?]
>   at akka.actor.ActorCell.invoke(ActorCell.scala:547) ~[?:?]
>   at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:270) ~[?:?]
>   at akka.dispatch.Mailbox.run(Mailbox.scala:231) ~[?:?]
>   at akka.dispatch.Mailbox.exec(Mailbox.scala:243) ~[?:?]
>   at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) 
> [?:1.8.0_362]
>   at 
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) 
> [?:1.8.0_362]
>   at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) 
> [?:1.8.0_362]
>   at 
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175) 
> [?:1.8.0_362]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)