[jira] [Updated] (FLINK-14234) All partition consumable events should be notified to SchedulingStrategy (SchedulerNG)

[ https://issues.apache.org/jira/browse/FLINK-14234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14234: Description: {{SchedulingStrategy}} requires partition consumable notification to make scheduling decisio

[jira] [Created] (FLINK-17046) SavepointWriterITCase failed on travis

Zhu Zhu created FLINK-17046: --- Summary: SavepointWriterITCase failed on travis Key: FLINK-17046 URL: https://issues.apache.org/jira/browse/FLINK-17046 Project: Flink Issue Type: Bug Compon

[jira] [Closed] (FLINK-17046) SavepointWriterITCase failed on travis

[ https://issues.apache.org/jira/browse/FLINK-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-17046. --- Resolution: Duplicate > SavepointWriterITCase failed on travis > -- > >

[jira] [Commented] (FLINK-17046) SavepointWriterITCase failed on travis

[ https://issues.apache.org/jira/browse/FLINK-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078005#comment-17078005 ] Zhu Zhu commented on FLINK-17046: - Yes, it should be the same issue. I encountered it af

[jira] [Commented] (FLINK-17046) SavepointWriterITCase failed on travis

[ https://issues.apache.org/jira/browse/FLINK-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078011#comment-17078011 ] Zhu Zhu commented on FLINK-17046: - I tried the fix locally and it worked. > SavepointWr

[jira] [Created] (FLINK-17047) Simplify SchedulingStrategy#onPartitionConsumable(...) parameters

Zhu Zhu created FLINK-17047: --- Summary: Simplify SchedulingStrategy#onPartitionConsumable(...) parameters Key: FLINK-17047 URL: https://issues.apache.org/jira/browse/FLINK-17047 Project: Flink Issu

[jira] [Closed] (FLINK-14162) Unify SchedulerOperations#allocateSlotsAndDeploy implementation for all scheduling strategies

[ https://issues.apache.org/jira/browse/FLINK-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-14162. --- Resolution: Fixed Implemented via: c2c9297f9fc45c052bfb245bbca2d91d8da28c7f > Unify SchedulerOperations#all

[jira] [Updated] (FLINK-14234) All partition consumable events should be notified to SchedulingStrategy (SchedulerNG)

[ https://issues.apache.org/jira/browse/FLINK-14234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14234: Description: {{SchedulingStrategy}} requires partition consumable notification to make scheduling decisio

[jira] [Assigned] (FLINK-17047) Simplify SchedulingStrategy#onPartitionConsumable(...) parameters

[ https://issues.apache.org/jira/browse/FLINK-17047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-17047: --- Assignee: Zhu Zhu > Simplify SchedulingStrategy#onPartitionConsumable(...) parameters > ---

[jira] [Commented] (FLINK-15307) Subclasses of FailoverStrategy are easily confused with implementation classes of RestartStrategy

[ https://issues.apache.org/jira/browse/FLINK-15307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000660#comment-17000660 ] Zhu Zhu commented on FLINK-15307: - Agreed that we can change the class name to avoid con

[jira] [Commented] (FLINK-15307) Subclasses of FailoverStrategy are easily confused with implementation classes of RestartStrategy

[ https://issues.apache.org/jira/browse/FLINK-15307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000664#comment-17000664 ] Zhu Zhu commented on FLINK-15307: - Sure, I can ping him here after the pre-requisites ar

[jira] [Commented] (FLINK-15249) Improve PipelinedRegions calculation with Union Set

[ https://issues.apache.org/jira/browse/FLINK-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000686#comment-17000686 ] Zhu Zhu commented on FLINK-15249: - Hi [~nppoly], sorry but I'm still busy with some 1.10

[jira] [Commented] (FLINK-15320) JobManager crashes in the standalone model when cancelling job which subtask' status is scheduled

[ https://issues.apache.org/jira/browse/FLINK-15320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000718#comment-17000718 ] Zhu Zhu commented on FLINK-15320: - The PR is opened. [~trohrmann] I checked the code and

[jira] [Commented] (FLINK-15345) CurrentExecution and priorExecutions are inconsistent in the test case

[ https://issues.apache.org/jira/browse/FLINK-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000740#comment-17000740 ] Zhu Zhu commented on FLINK-15345: - >> When the length of priorExecutions does not exceed

[jira] [Commented] (FLINK-15325) Input location preference which affects task distribution may make certain job performance worse

[ https://issues.apache.org/jira/browse/FLINK-15325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000940#comment-17000940 ] Zhu Zhu commented on FLINK-15325: - Yes, if the config is enabled, {{ExecutionVertex#get

[jira] [Assigned] (FLINK-15354) Start and stop minikube only in kubernetes related e2e tests

[ https://issues.apache.org/jira/browse/FLINK-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15354: --- Assignee: Zhu Zhu > Start and stop minikube only in kubernetes related e2e tests >

[jira] [Assigned] (FLINK-15354) Start and stop minikube only in kubernetes related e2e tests

[ https://issues.apache.org/jira/browse/FLINK-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15354: --- Assignee: Yang Wang (was: Zhu Zhu) > Start and stop minikube only in kubernetes related e2e tests

[jira] [Commented] (FLINK-15354) Start and stop minikube only in kubernetes related e2e tests

[ https://issues.apache.org/jira/browse/FLINK-15354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002590#comment-17002590 ] Zhu Zhu commented on FLINK-15354: - Thanks [~fly_in_gis] for reporting this issue. I have

[jira] [Assigned] (FLINK-15364) Introduce streaming task using heap backend e2e tests for Mesos

[ https://issues.apache.org/jira/browse/FLINK-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15364: --- Assignee: Yangze Guo > Introduce streaming task using heap backend e2e tests for Mesos > --

[jira] [Assigned] (FLINK-15367) Handle backwards compatibility of "taskmanager.heap.size" differently for standalone / active setups

[ https://issues.apache.org/jira/browse/FLINK-15367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15367: --- Assignee: Xintong Song > Handle backwards compatibility of "taskmanager.heap.size" differently for

[jira] [Assigned] (FLINK-15365) Introduce streaming task using rocksDB backend e2e tests for Mesos

[ https://issues.apache.org/jira/browse/FLINK-15365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15365: --- Assignee: Yangze Guo > Introduce streaming task using rocksDB backend e2e tests for Mesos > ---

[jira] [Assigned] (FLINK-15369) MiniCluster use fixed network / managed memory sizes by defualt

[ https://issues.apache.org/jira/browse/FLINK-15369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15369: --- Assignee: Xintong Song > MiniCluster use fixed network / managed memory sizes by defualt >

[jira] [Assigned] (FLINK-15373) Update descriptions for framework / task off-heap memory config options

[ https://issues.apache.org/jira/browse/FLINK-15373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15373: --- Assignee: Xintong Song > Update descriptions for framework / task off-heap memory config options >

[jira] [Assigned] (FLINK-15372) Use shorter config keys for FLIP-49 total memory config options

[ https://issues.apache.org/jira/browse/FLINK-15372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15372: --- Assignee: Xintong Song > Use shorter config keys for FLIP-49 total memory config options >

[jira] [Assigned] (FLINK-15371) Change FLIP-49 memory configurations to use the new memory type config options

[ https://issues.apache.org/jira/browse/FLINK-15371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15371: --- Assignee: Xintong Song > Change FLIP-49 memory configurations to use the new memory type config opt

[jira] [Assigned] (FLINK-15374) Update descriptions for jvm overhead config options

[ https://issues.apache.org/jira/browse/FLINK-15374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15374: --- Assignee: Xintong Song > Update descriptions for jvm overhead config options >

[jira] [Assigned] (FLINK-15375) Improve MemorySize to print / parse with better readability.

[ https://issues.apache.org/jira/browse/FLINK-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15375: --- Assignee: Xintong Song > Improve MemorySize to print / parse with better readability. > ---

[jira] [Closed] (FLINK-13662) FlinkKinesisProducerTest.testBackpressure failed on Travis

[ https://issues.apache.org/jira/browse/FLINK-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-13662. --- Resolution: Fixed Fixed via master: a62641a0918aaedbac6312293cf8826e4d11f300 20041cafbfe500ed386e11da5d09f1

[jira] [Assigned] (FLINK-15377) Mesos WordCount test fails on travis

[ https://issues.apache.org/jira/browse/FLINK-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15377: --- Assignee: Yangze Guo > Mesos WordCount test fails on travis >

[jira] [Closed] (FLINK-11524) LeaderChangeClusterComponentsTest.testReelectionOfJobMaster failed on Travis

[ https://issues.apache.org/jira/browse/FLINK-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-11524. --- Resolution: Later #10553 is merged to make the error more descriptive for trouble shooting. master: 5e5cdd84

[jira] [Commented] (FLINK-15377) Mesos WordCount test fails on travis

[ https://issues.apache.org/jira/browse/FLINK-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003085#comment-17003085 ] Zhu Zhu commented on FLINK-15377: - Fixed via master: 3036dd97eef4d1451baf6984885ad37843

[jira] [Closed] (FLINK-15377) Mesos WordCount test fails on travis

[ https://issues.apache.org/jira/browse/FLINK-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-15377. --- Resolution: Fixed > Mesos WordCount test fails on travis > > >

[jira] [Closed] (FLINK-15374) Update descriptions for jvm overhead config options

[ https://issues.apache.org/jira/browse/FLINK-15374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-15374. --- Resolution: Fixed Fixed via master: e9c8282becb947ec230893b3e212153118ffc7b1 release-1.10: d9d75d8b0f56133

[jira] [Closed] (FLINK-15373) Update descriptions for framework / task off-heap memory config options

[ https://issues.apache.org/jira/browse/FLINK-15373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-15373. --- Resolution: Fixed Fixed via: master: 768be4f9bc31bcd38053c896af92f4af7a212144 66da8eb710b2700f46747b7775400

[jira] [Closed] (FLINK-15372) Use shorter config keys for FLIP-49 total memory config options

[ https://issues.apache.org/jira/browse/FLINK-15372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-15372. --- Resolution: Fixed Fixed via: master: 82619f260af0b24ff8244a14f8fc84816edae083 0ba4a2b4cc2b48886d5a7948d631e

[jira] [Commented] (FLINK-15394) in yarn mode, jobmanager fails to start in case of rest.port conflict.

[ https://issues.apache.org/jira/browse/FLINK-15394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003426#comment-17003426 ] Zhu Zhu commented on FLINK-15394: - Hi [~watters_fish], I think it is not a bug. If a use

[jira] [Updated] (FLINK-14163) Execution#producedPartitions is possibly not assigned when deploying tasks with DefaultScheduler

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14163: Summary: Execution#producedPartitions is possibly not assigned when deploying tasks with DefaultScheduler

[jira] [Updated] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14163: Summary: Execution#producedPartitions is possibly not assigned when used (was: Execution#producedPartitio

[jira] [Assigned] (FLINK-15427) State TTL RocksDb backend end-to-end test stalls on travis

[ https://issues.apache.org/jira/browse/FLINK-15427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15427: --- Assignee: Congxian Qiu(klion26) > State TTL RocksDb backend end-to-end test stalls on travis >

[jira] [Created] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

Zhu Zhu created FLINK-15456: --- Summary: Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests Key: FLINK-15456 URL: https://issues.apache.org/jira/browse/FLINK-15456

[jira] [Commented] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006696#comment-17006696 ] Zhu Zhu commented on FLINK-15456: - This issue looks like the case described in FLINK-135

[jira] [Comment Edited] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006696#comment-17006696 ] Zhu Zhu edited comment on FLINK-15456 at 1/2/20 9:41 AM: - [~xint

[jira] [Updated] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-15456: Attachment: jm_part2.log > Job keeps failing on slot allocation timeout due to RM not allocating new TMs

[jira] [Commented] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006719#comment-17006719 ] Zhu Zhu commented on FLINK-15456: - Thanks for the explanation [~xintongsong]. I still h

[jira] [Commented] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006721#comment-17006721 ] Zhu Zhu commented on FLINK-15448: - TBH, I think it's not very necessary to add the host

[jira] [Commented] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006779#comment-17006779 ] Zhu Zhu commented on FLINK-15456: - [~xintongsong], in this case, the RM recovered withou

[jira] [Commented] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006798#comment-17006798 ] Zhu Zhu commented on FLINK-15448: - Hi Victor, have you investigated which logs should be

[jira] [Comment Edited] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006798#comment-17006798 ] Zhu Zhu edited comment on FLINK-15448 at 1/2/20 1:01 PM: - [~vict

[jira] [Updated] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14163: Description: Currently {{Execution#producedPartitions}} is assigned after the partitions have completed t

[jira] [Updated] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14163: Description: Currently {{Execution#producedPartitions}} is assigned after the partitions have completed t

[jira] [Commented] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007187#comment-17007187 ] Zhu Zhu commented on FLINK-15456: - [~xintongsong], the RM was not really revoked leaders

[jira] [Commented] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007193#comment-17007193 ] Zhu Zhu commented on FLINK-15456: - Synced with [~xintongsong] offline, the RM recovered

[jira] [Commented] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007198#comment-17007198 ] Zhu Zhu commented on FLINK-15448: - [~victor-wong], have you investigated which logs shou

[jira] [Commented] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007302#comment-17007302 ] Zhu Zhu commented on FLINK-15448: - How could we get the host of a ResourceID in {{org.a

[jira] [Commented] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008606#comment-17008606 ] Zhu Zhu commented on FLINK-14163: - Thanks [~zjwang] for the feedbacks. I think partition

[jira] [Closed] (FLINK-14572) BlobsCleanupITCase failed on Travis

[ https://issues.apache.org/jira/browse/FLINK-14572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-14572. --- Resolution: Cannot Reproduce [~gaoyunhaii] added some detailed logs when the case fails. Close this ticket

[jira] [Commented] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009471#comment-17009471 ] Zhu Zhu commented on FLINK-14163: - +1 to the solution proposed by [~azagrebin]. The fix

[jira] [Created] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

Zhu Zhu created FLINK-15499: --- Summary: No debug log describes the host of a TM before any task is deployed to it in YARN mode Key: FLINK-15499 URL: https://issues.apache.org/jira/browse/FLINK-15499 Projec

[jira] [Commented] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

[ https://issues.apache.org/jira/browse/FLINK-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009575#comment-17009575 ] Zhu Zhu commented on FLINK-15499: - [~xintongsong] would you help to confirm if it is rea

[jira] [Updated] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

[ https://issues.apache.org/jira/browse/FLINK-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-15499: Description: When troubleshooting FLINK-15456, I noticed a TM hang in starting and not able to register t

[jira] [Updated] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-15456: Attachment: jm.log tm_container_07.log > Job keeps failing on slot allocation timeout due

[jira] [Commented] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009644#comment-17009644 ] Zhu Zhu commented on FLINK-15456: - I just reproduced the issue with debug logs enabled.

[jira] [Commented] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009799#comment-17009799 ] Zhu Zhu commented on FLINK-14163: - Makes sense. Unexpected blocked main thread can be ha

[jira] [Assigned] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

[ https://issues.apache.org/jira/browse/FLINK-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15499: --- Assignee: Xintong Song > No debug log describes the host of a TM before any task is deployed to it

[jira] [Commented] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

[ https://issues.apache.org/jira/browse/FLINK-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010286#comment-17010286 ] Zhu Zhu commented on FLINK-15499: - I agree that make this log info would help, especiall

[jira] [Commented] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010312#comment-17010312 ] Zhu Zhu commented on FLINK-15448: - I just met another case that one can even no be able

[jira] [Commented] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010320#comment-17010320 ] Zhu Zhu commented on FLINK-15448: - [~xintongsong] agreed that we should take a lot care

[jira] [Updated] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

[ https://issues.apache.org/jira/browse/FLINK-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-15499: Fix Version/s: 1.10.0 > No debug log describes the host of a TM before any task is deployed to it in > Y

[jira] [Commented] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

[ https://issues.apache.org/jira/browse/FLINK-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010444#comment-17010444 ] Zhu Zhu commented on FLINK-15499: - Fixed via: master: 9df5c80e7e729f49595ef681446216583

[jira] [Resolved] (FLINK-15499) No debug log describes the host of a TM before any task is deployed to it in YARN mode

[ https://issues.apache.org/jira/browse/FLINK-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu resolved FLINK-15499. - Resolution: Fixed > No debug log describes the host of a TM before any task is deployed to it in > YAR

[jira] [Updated] (FLINK-15456) Job keeps failing on slot allocation timeout due to RM not allocating new TMs for slot requests

[ https://issues.apache.org/jira/browse/FLINK-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-15456: Priority: Critical (was: Blocker) > Job keeps failing on slot allocation timeout due to RM not allocating

[jira] [Closed] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-14058. --- Release Note: The memory configs for table operators, including * table.exec.resource.external-buffer-memo

[jira] [Commented] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010516#comment-17010516 ] Zhu Zhu commented on FLINK-14058: - Hi [~lzljs3620320], would you help to verify the rele

[jira] [Updated] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14058: Release Note: The memory configs for table operators are weight hints now rather than absolute memory req

[jira] [Commented] (FLINK-13554) ResourceManager should have a timeout on starting new TaskExecutors.

[ https://issues.apache.org/jira/browse/FLINK-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010522#comment-17010522 ] Zhu Zhu commented on FLINK-13554: - This issue is triggered only when a TM is stuck in la

[jira] [Updated] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14058: Release Note: The memory configs for table operators are weight hints now rather than absolute memory req

[jira] [Commented] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010529#comment-17010529 ] Zhu Zhu commented on FLINK-14058: - [~lzljs3620320], Thanks a lot! Updated the release no

[jira] [Updated] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14058: Release Note: The memory configs for table operators are weight hints now rather than absolute memory req

[jira] [Updated] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14058: Release Note: The memory configs for table operators are weight hints now rather than absolute memory req

[jira] [Updated] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14058: Release Note: The memory configs for table operators are weight hints now rather than absolute memory req

[jira] [Commented] (FLINK-15448) Log host informations for TaskManager failures.

[ https://issues.apache.org/jira/browse/FLINK-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010537#comment-17010537 ] Zhu Zhu commented on FLINK-15448: - [~victor-wong] not pretty sure what's the benefit to

[jira] [Updated] (FLINK-14058) FLIP-53 Fine Grained Operator Resource Management

[ https://issues.apache.org/jira/browse/FLINK-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14058: Release Note: The memory configs for table operators are no longer absolute memory requirements but weigh

[jira] [Commented] (FLINK-15522) Misleading root cause exception when cancelling the job

[ https://issues.apache.org/jira/browse/FLINK-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011522#comment-17011522 ] Zhu Zhu commented on FLINK-15522: - I think the reason why this happens is that in {{JobR

[jira] [Comment Edited] (FLINK-15522) Misleading root cause exception when cancelling the job

[ https://issues.apache.org/jira/browse/FLINK-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011522#comment-17011522 ] Zhu Zhu edited comment on FLINK-15522 at 1/9/20 7:52 AM: - I thin

[jira] [Comment Edited] (FLINK-15522) Misleading root cause exception when cancelling the job

[ https://issues.apache.org/jira/browse/FLINK-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011522#comment-17011522 ] Zhu Zhu edited comment on FLINK-15522 at 1/9/20 7:53 AM: - I thin

[jira] [Commented] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011647#comment-17011647 ] Zhu Zhu commented on FLINK-14163: - Thanks [~ym] for trying out the solutions. I'd prefer

[jira] [Comment Edited] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011647#comment-17011647 ] Zhu Zhu edited comment on FLINK-14163 at 1/9/20 10:09 AM: -- Than

[jira] [Commented] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011692#comment-17011692 ] Zhu Zhu commented on FLINK-14163: - [~chesnay] The deployment issue can happen with ng sc

[jira] [Commented] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011878#comment-17011878 ] Zhu Zhu commented on FLINK-14163: - Thanks [~chesnay] for the update! Then we are now tak

[jira] [Commented] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011944#comment-17011944 ] Zhu Zhu commented on FLINK-14163: - Oh I understand what your mean. Previously [~azagreb

[jira] [Comment Edited] (FLINK-14163) Execution#producedPartitions is possibly not assigned when used

[ https://issues.apache.org/jira/browse/FLINK-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011944#comment-17011944 ] Zhu Zhu edited comment on FLINK-14163 at 1/9/20 3:23 PM: - Oh I u

[jira] [Commented] (FLINK-15522) Misleading root cause exception when cancelling the job

[ https://issues.apache.org/jira/browse/FLINK-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012396#comment-17012396 ] Zhu Zhu commented on FLINK-15522: - I will take this issue then and open a PR soon. > Mi

[jira] [Assigned] (FLINK-15522) Misleading root cause exception when cancelling the job

[ https://issues.apache.org/jira/browse/FLINK-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu reassigned FLINK-15522: --- Assignee: Zhu Zhu > Misleading root cause exception when cancelling the job > -

[jira] [Updated] (FLINK-15522) Misleading root cause exception when cancelling the job

[ https://issues.apache.org/jira/browse/FLINK-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-15522: Affects Version/s: 1.9.1 > Misleading root cause exception when cancelling the job > -

[jira] [Closed] (FLINK-15522) Misleading root cause exception when cancelling the job

[ https://issues.apache.org/jira/browse/FLINK-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-15522. --- Fix Version/s: 1.11.0 1.10.0 1.9.2 Resolution: Fixed Fixed via:

[jira] [Commented] (FLINK-15568) RestartPipelinedRegionStrategy: not ensure the EXACTLY_ONCE semantics, in 1.8 versions

[ https://issues.apache.org/jira/browse/FLINK-15568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014212#comment-17014212 ] Zhu Zhu commented on FLINK-15568: - Hi [~andrew_lin], RestartPipelinedRegionStrategy is e

[jira] [Comment Edited] (FLINK-15568) RestartPipelinedRegionStrategy: not ensure the EXACTLY_ONCE semantics, in 1.8 versions

[ https://issues.apache.org/jira/browse/FLINK-15568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014212#comment-17014212 ] Zhu Zhu edited comment on FLINK-15568 at 1/13/20 10:51 AM: --- Hi

[jira] [Closed] (FLINK-15568) RestartPipelinedRegionStrategy: not ensure the EXACTLY_ONCE semantics, in 1.8 versions

[ https://issues.apache.org/jira/browse/FLINK-15568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu closed FLINK-15568. --- Resolution: Won't Fix > RestartPipelinedRegionStrategy: not ensure the EXACTLY_ONCE semantics, in 1.8 > ver

[jira] [Commented] (FLINK-15568) RestartPipelinedRegionStrategy: not ensure the EXACTLY_ONCE semantics, in 1.8 versions

[ https://issues.apache.org/jira/browse/FLINK-15568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014795#comment-17014795 ] Zhu Zhu commented on FLINK-15568: - Sure. Issue is closed. > RestartPipelinedRegionStrat

[jira] [Commented] (FLINK-15307) Subclasses of FailoverStrategy are easily confused with implementation classes of RestartStrategy

[ https://issues.apache.org/jira/browse/FLINK-15307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014799#comment-17014799 ] Zhu Zhu commented on FLINK-15307: - The legacy failover strategies will be removed in 1.1

<    2   3   4   5   6   7   8   9   10   11   >