[jira] [Comment Edited] (FLINK-18695) Allow NettyBufferPool to allocate heap buffers

[ https://issues.apache.org/jira/browse/FLINK-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167650#comment-17167650 ] Zhijiang edited comment on FLINK-18695 at 7/30/20, 5:58 AM: {quote} Do we

[jira] [Comment Edited] (FLINK-18695) Allow NettyBufferPool to allocate heap buffers

[ https://issues.apache.org/jira/browse/FLINK-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167650#comment-17167650 ] Zhijiang edited comment on FLINK-18695 at 7/30/20, 5:58 AM: {quote} Do we

[jira] [Comment Edited] (FLINK-18695) Allow NettyBufferPool to allocate heap buffers

[ https://issues.apache.org/jira/browse/FLINK-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167650#comment-17167650 ] Zhijiang edited comment on FLINK-18695 at 7/30/20, 5:55 AM: >Do we actually

[jira] [Commented] (FLINK-18695) Allow NettyBufferPool to allocate heap buffers

[ https://issues.apache.org/jira/browse/FLINK-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167650#comment-17167650 ] Zhijiang commented on FLINK-18695: -- > Do we actually also cover the receiving side and use our own

[jira] [Closed] (FLINK-18595) Deadlock during job shutdown

[ https://issues.apache.org/jira/browse/FLINK-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18595. Resolution: Fixed Merged in master: c137102eb05e438bd97ec5e397ecb3d17342e6c1 Merged in release-1.11:

[jira] [Commented] (FLINK-18695) Allow NettyBufferPool to allocate heap buffers

[ https://issues.apache.org/jira/browse/FLINK-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166914#comment-17166914 ] Zhijiang commented on FLINK-18695: -- I agree with [~sewen]'s above analysis. Regarding the proposed

[jira] [Commented] (FLINK-18662) Provide more detailed metrics why unaligned checkpoint is taking long time

[ https://issues.apache.org/jira/browse/FLINK-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166171#comment-17166171 ] Zhijiang commented on FLINK-18662: -- Thanks for explanation [~pnowojski]! I get the point now. Yes,

[jira] [Commented] (FLINK-18662) Provide more detailed metrics why unaligned checkpoint is taking long time

[ https://issues.apache.org/jira/browse/FLINK-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166140#comment-17166140 ] Zhijiang commented on FLINK-18662: -- The 1 and 2 are consistent with my above proposals. For the 3, is

[jira] [Commented] (FLINK-18662) Provide more detailed metrics why unaligned checkpoint is taking long time

[ https://issues.apache.org/jira/browse/FLINK-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165485#comment-17165485 ] Zhijiang commented on FLINK-18662: -- I agree that adding the metrics for alignment duration and

[jira] [Commented] (FLINK-16404) Avoid caching buffers for blocked input channels before barrier alignment

[ https://issues.apache.org/jira/browse/FLINK-16404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165452#comment-17165452 ] Zhijiang commented on FLINK-16404: -- Yes, that is our intention to not remove this metric from web UI

[jira] [Commented] (FLINK-17095) KafkaProducerExactlyOnceITCase fails with "address already in use"

[ https://issues.apache.org/jira/browse/FLINK-17095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161817#comment-17161817 ] Zhijiang commented on FLINK-17095: -- Thanks for fixing [~ym], closed it. >

[jira] [Closed] (FLINK-17095) KafkaProducerExactlyOnceITCase fails with "address already in use"

[ https://issues.apache.org/jira/browse/FLINK-17095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-17095. Resolution: Duplicate > KafkaProducerExactlyOnceITCase fails with "address already in use" >

[jira] [Closed] (FLINK-10462) Remove ConnectionIndex for further sharing tcp connection in credit-based mode

[ https://issues.apache.org/jira/browse/FLINK-10462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-10462. Resolution: Not A Problem Close it now for cleanup unless we find it necessary to reopen it future. >

[jira] [Closed] (FLINK-11037) Introduce another greedy mechanism for distributing floating buffers

[ https://issues.apache.org/jira/browse/FLINK-11037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-11037. Resolution: Later I guess we do not have much time to further work on it recently as there are no

[jira] [Closed] (FLINK-13126) Construct special test/benchmark to verify the backlog effect

[ https://issues.apache.org/jira/browse/FLINK-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-13126. Resolution: Not A Problem > Construct special test/benchmark to verify the backlog effect >

[jira] [Commented] (FLINK-13126) Construct special test/benchmark to verify the backlog effect

[ https://issues.apache.org/jira/browse/FLINK-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161790#comment-17161790 ] Zhijiang commented on FLINK-13126: -- Close it temporarily for cleanup since it seems not very necessary

[jira] [Closed] (FLINK-11035) Notify data available to network stack immediately after finishing BufferBuilder

[ https://issues.apache.org/jira/browse/FLINK-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-11035. Resolution: Won't Fix As discussed before, it seems no evidence/necessary to improve it ATM. So close it

[jira] [Commented] (FLINK-17073) Slow checkpoint cleanup causing OOMs

[ https://issues.apache.org/jira/browse/FLINK-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161704#comment-17161704 ] Zhijiang commented on FLINK-17073: -- I have assigned it to [~echauchot] > Slow checkpoint cleanup

[jira] [Assigned] (FLINK-17073) Slow checkpoint cleanup causing OOMs

[ https://issues.apache.org/jira/browse/FLINK-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-17073: Assignee: Etienne Chauchot > Slow checkpoint cleanup causing OOMs >

[jira] [Updated] (FLINK-18595) Deadlock during job shutdown

[ https://issues.apache.org/jira/browse/FLINK-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18595: - Fix Version/s: 1.11.2 1.12.0 > Deadlock during job shutdown >

[jira] [Updated] (FLINK-18595) Deadlock during job shutdown

[ https://issues.apache.org/jira/browse/FLINK-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18595: - Affects Version/s: 1.11.1 > Deadlock during job shutdown > > >

[jira] [Updated] (FLINK-18595) Deadlock during job shutdown

[ https://issues.apache.org/jira/browse/FLINK-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18595: - Affects Version/s: 1.11.0 > Deadlock during job shutdown > > >

[jira] [Assigned] (FLINK-18612) WordCount example failure when setting relative output path

[ https://issues.apache.org/jira/browse/FLINK-18612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18612: Assignee: Yun Gao > WordCount example failure when setting relative output path >

[jira] [Created] (FLINK-18612) WordCount example failure when using relative output path

Zhijiang created FLINK-18612: Summary: WordCount example failure when using relative output path Key: FLINK-18612 URL: https://issues.apache.org/jira/browse/FLINK-18612 Project: Flink Issue

[jira] [Updated] (FLINK-18612) WordCount example failure when setting relative output path

[ https://issues.apache.org/jira/browse/FLINK-18612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18612: - Summary: WordCount example failure when setting relative output path (was: WordCount example failure

[jira] [Commented] (FLINK-18595) Deadlock during job shutdown

[ https://issues.apache.org/jira/browse/FLINK-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157944#comment-17157944 ] Zhijiang commented on FLINK-18595: -- Thanks for reporting this [~dian.fu]. It is caused by concurrently

[jira] [Assigned] (FLINK-18595) Deadlock during job shutdown

[ https://issues.apache.org/jira/browse/FLINK-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18595: Assignee: Zhijiang > Deadlock during job shutdown > > >

[jira] [Updated] (FLINK-17636) SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read from released RecoveredInputChannel

[ https://issues.apache.org/jira/browse/FLINK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-17636: - Affects Version/s: 1.11.0 > SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to

[jira] [Updated] (FLINK-17636) SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read from released RecoveredInputChannel

[ https://issues.apache.org/jira/browse/FLINK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-17636: - Fix Version/s: 1.11.0 > SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read

[jira] [Closed] (FLINK-17636) SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read from released RecoveredInputChannel

[ https://issues.apache.org/jira/browse/FLINK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-17636. Resolution: Fixed Merged in release-1.11: 57e57624deded5594749cbccf17a5878c6dc81b8 Merged in master:

[jira] [Closed] (FLINK-18591) Fix the format issue for metrics web page

[ https://issues.apache.org/jira/browse/FLINK-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18591. Resolution: Fixed Merged in release-1.11: d6473f32aa159c6242e4293a60be179135f0e1f2 Merged in master:

[jira] [Created] (FLINK-18591) Fix the format issue for metrics web page

Zhijiang created FLINK-18591: Summary: Fix the format issue for metrics web page Key: FLINK-18591 URL: https://issues.apache.org/jira/browse/FLINK-18591 Project: Flink Issue Type: Bug

[jira] [Assigned] (FLINK-18552) Update migration tests in master to cover migration from release-1.11

[ https://issues.apache.org/jira/browse/FLINK-18552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18552: Assignee: Yun Gao > Update migration tests in master to cover migration from release-1.11 >

[jira] [Created] (FLINK-18552) Update migration tests in master to cover migration from release-1.11

Zhijiang created FLINK-18552: Summary: Update migration tests in master to cover migration from release-1.11 Key: FLINK-18552 URL: https://issues.apache.org/jira/browse/FLINK-18552 Project: Flink

[jira] [Commented] (FLINK-17636) SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read from released RecoveredInputChannel

[ https://issues.apache.org/jira/browse/FLINK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153176#comment-17153176 ] Zhijiang commented on FLINK-17636: -- Thanks for reporting this, I will reopen it to investigate. >

[jira] [Reopened] (FLINK-17636) SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read from released RecoveredInputChannel

[ https://issues.apache.org/jira/browse/FLINK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reopened FLINK-17636: -- > SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read > from released

[jira] [Updated] (FLINK-15416) Add Retry Mechanism for PartitionRequestClientFactory.ConnectingChannel

[ https://issues.apache.org/jira/browse/FLINK-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-15416: - Affects Version/s: 1.11.1 1.11.0 1.10.1 > Add Retry

[jira] [Updated] (FLINK-15416) Add Retry Mechanism for PartitionRequestClientFactory.ConnectingChannel

[ https://issues.apache.org/jira/browse/FLINK-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-15416: - Fix Version/s: 1.12.0 > Add Retry Mechanism for PartitionRequestClientFactory.ConnectingChannel >

[jira] [Closed] (FLINK-15416) Add Retry Mechanism for PartitionRequestClientFactory.ConnectingChannel

[ https://issues.apache.org/jira/browse/FLINK-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-15416. Merged in master: 0175bf5d69013a48eb501d78ac7a231c9fa335c1 > Add Retry Mechanism for

[jira] [Updated] (FLINK-15416) Add Retry Mechanism for PartitionRequestClientFactory.ConnectingChannel

[ https://issues.apache.org/jira/browse/FLINK-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-15416: - Issue Type: Improvement (was: Wish) > Add Retry Mechanism for

[jira] [Closed] (FLINK-18336) CheckpointFailureManager forgets failed checkpoints after a successful one

[ https://issues.apache.org/jira/browse/FLINK-18336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18336. Resolution: Fixed Merged in master: 06af98a6e0247dbf1b08f5caf6ca67f2a56dd8e5 > CheckpointFailureManager

[jira] [Updated] (FLINK-18336) CheckpointFailureManager forgets failed checkpoints after a successful one

[ https://issues.apache.org/jira/browse/FLINK-18336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18336: - Fix Version/s: 1.12.0 > CheckpointFailureManager forgets failed checkpoints after a successful one >

[jira] [Closed] (FLINK-4911) Non-disruptive JobManager Failures via Reconciliation

[ https://issues.apache.org/jira/browse/FLINK-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-4911. --- Resolution: Later > Non-disruptive JobManager Failures via Reconciliation >

[jira] [Closed] (FLINK-18064) Update documentation taking unaligned checkpoints into the account

[ https://issues.apache.org/jira/browse/FLINK-18064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18064. Resolution: Fixed Merged in release-1.11: 5afb3a68ccb370a9f77649f89f0fcb22dc02fc06,

[jira] [Closed] (FLINK-18116) Manually test E2E performance on Flink 1.11

[ https://issues.apache.org/jira/browse/FLINK-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18116. Resolution: Done > Manually test E2E performance on Flink 1.11 >

[jira] [Closed] (FLINK-13753) Integrate new Source Operator with Mailbox Model in StreamTask

[ https://issues.apache.org/jira/browse/FLINK-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-13753. Resolution: Done > Integrate new Source Operator with Mailbox Model in StreamTask >

[jira] [Updated] (FLINK-13753) Integrate new Source Operator with Mailbox Model in StreamTask

[ https://issues.apache.org/jira/browse/FLINK-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-13753: - Priority: Major (was: Minor) > Integrate new Source Operator with Mailbox Model in StreamTask >

[jira] [Closed] (FLINK-13754) Decouple OperatorChain with StreamStatusMaintainer

[ https://issues.apache.org/jira/browse/FLINK-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-13754. Resolution: Won't Fix > Decouple OperatorChain with StreamStatusMaintainer >

[jira] [Closed] (FLINK-18088) Umbrella for testing features in release-1.11.0

[ https://issues.apache.org/jira/browse/FLINK-18088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18088. Resolution: Done > Umbrella for testing features in release-1.11.0 >

[jira] [Commented] (FLINK-18433) From the end-to-end performance test results, 1.11 has a regression

[ https://issues.apache.org/jira/browse/FLINK-18433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147180#comment-17147180 ] Zhijiang commented on FLINK-18433: -- Thanks for all the above analysis. >From my side, there are

[jira] [Commented] (FLINK-18427) Job failed under java 11

[ https://issues.apache.org/jira/browse/FLINK-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144996#comment-17144996 ] Zhijiang commented on FLINK-18427: -- Fully agree with [~sewen]'s above analysis. In addition, we also

[jira] [Assigned] (FLINK-18399) TableResult#print can not print the result of unbounded stream query

[ https://issues.apache.org/jira/browse/FLINK-18399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18399: Assignee: Zhijiang > TableResult#print can not print the result of unbounded stream query >

[jira] [Assigned] (FLINK-18399) TableResult#print can not print the result of unbounded stream query

[ https://issues.apache.org/jira/browse/FLINK-18399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18399: Assignee: godfrey he (was: Zhijiang) > TableResult#print can not print the result of unbounded

[jira] [Commented] (FLINK-18365) The same sql in a batch env and a streaming env has different value.

[ https://issues.apache.org/jira/browse/FLINK-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142599#comment-17142599 ] Zhijiang commented on FLINK-18365: -- [~jark] Do you think it would be a blocker issue for release? The

[jira] [Commented] (FLINK-18364) A streaming sql cause "org.apache.flink.table.api.ValidationException: Type TIMESTAMP(6) of table field 'rowtime' does not match with the physical type TIMESTAMP(3) of

[ https://issues.apache.org/jira/browse/FLINK-18364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142595#comment-17142595 ] Zhijiang commented on FLINK-18364: --  [~lzljs3620320] is in vacation these days. [~ykt836] [~jark] could

[jira] [Commented] (FLINK-18371) NPE of "org.apache.flink.table.data.util.DataFormatConverters$BigDecimalConverter.toExternalImpl(DataFormatConverters.java:680)"

[ https://issues.apache.org/jira/browse/FLINK-18371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142588#comment-17142588 ] Zhijiang commented on FLINK-18371: -- [~caoshaokan] [~libenchao], If this is really a bug, could you

[jira] [Commented] (FLINK-18400) A streaming sql has "java.lang.NegativeArraySizeException"

[ https://issues.apache.org/jira/browse/FLINK-18400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142584#comment-17142584 ] Zhijiang commented on FLINK-18400: -- [~jark] [~ykt836], could you check whether it is in your scope and

[jira] [Updated] (FLINK-18411) CollectionExecutorTest failed to compiled in release-1.11

[ https://issues.apache.org/jira/browse/FLINK-18411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18411: - Issue Type: Task (was: Bug) > CollectionExecutorTest failed to compiled in release-1.11 >

[jira] [Assigned] (FLINK-18116) Manually test E2E performance on Flink 1.11

[ https://issues.apache.org/jira/browse/FLINK-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18116: Assignee: Aihua Li (was: Zhijiang) > Manually test E2E performance on Flink 1.11 >

[jira] [Assigned] (FLINK-18116) Manually test E2E performance on Flink 1.11

[ https://issues.apache.org/jira/browse/FLINK-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18116: Assignee: Zhijiang (was: Aihua Li) > Manually test E2E performance on Flink 1.11 >

[jira] [Assigned] (FLINK-18115) Manually test fault-tolerance stability on Flink 1.11

[ https://issues.apache.org/jira/browse/FLINK-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18115: Assignee: Aihua Li (was: Zhijiang) > Manually test fault-tolerance stability on Flink 1.11 >

[jira] [Assigned] (FLINK-18115) Manually test fault-tolerance stability on Flink 1.11

[ https://issues.apache.org/jira/browse/FLINK-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18115: Assignee: Zhijiang (was: Aihua Li) > Manually test fault-tolerance stability on Flink 1.11 >

[jira] [Assigned] (FLINK-18313) Update Hive dialect doc about VIEW

[ https://issues.apache.org/jira/browse/FLINK-18313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18313: Assignee: Rui Li (was: Zhijiang) > Update Hive dialect doc about VIEW >

[jira] [Assigned] (FLINK-18313) Update Hive dialect doc about VIEW

[ https://issues.apache.org/jira/browse/FLINK-18313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18313: Assignee: Rui Li (was: Rui Li) > Update Hive dialect doc about VIEW >

[jira] [Assigned] (FLINK-18313) Update Hive dialect doc about VIEW

[ https://issues.apache.org/jira/browse/FLINK-18313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18313: Assignee: Zhijiang (was: Rui Li) > Update Hive dialect doc about VIEW >

[jira] [Assigned] (FLINK-18313) Update Hive dialect doc about VIEW

[ https://issues.apache.org/jira/browse/FLINK-18313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reassigned FLINK-18313: Assignee: Rui Li > Update Hive dialect doc about VIEW > -- > >

[jira] [Commented] (FLINK-18348) RemoteInputChannel should checkError before checking partitionRequestClient

[ https://issues.apache.org/jira/browse/FLINK-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17139308#comment-17139308 ] Zhijiang commented on FLINK-18348: -- [~wind_ljy] You are right, my previous mentioned usages will not

[jira] [Commented] (FLINK-18348) RemoteInputChannel should checkError before checking partitionRequestClient

[ https://issues.apache.org/jira/browse/FLINK-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138999#comment-17138999 ] Zhijiang commented on FLINK-18348: -- [~pnowojski] FLINK-16536 might cause this issue, but there was also

[jira] [Closed] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18238. Resolution: Fixed Master: 07772bdb9abc0bcd3b3c8869f6abdc8088bd7cea Release-1.11: 

[jira] [Updated] (FLINK-18088) Umbrella for testing features in release-1.11.0

[ https://issues.apache.org/jira/browse/FLINK-18088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18088: - Priority: Critical (was: Blocker) > Umbrella for testing features in release-1.11.0 >

[jira] [Commented] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135695#comment-17135695 ] Zhijiang commented on FLINK-18238: -- bq. RPC abort notifications were introduced in 1.11 but we've

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:36 AM: bq. Ok I get it.

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:36 AM: bq. Ok I get it.

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:35 AM: ??Ok I get it.

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:35 AM: >> Ok I get it.

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:35 AM: ??Ok I get it.

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:33 AM: Ok I get it. It

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:33 AM: Ok I get it. It

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:32 AM: Ok I get it. It

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:32 AM: Ok I get it. It

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:32 AM: Ok I get it. It

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:31 AM: Ok I get it. It

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:31 AM: Ok I get it. It

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:29 AM: > Ok I get it.

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 9:29 AM: > Ok I get it.

[jira] [Commented] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135667#comment-17135667 ] Zhijiang commented on FLINK-18238: -- > Ok I get it. It would be I think OK to cancel the alignment

[jira] [Commented] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135502#comment-17135502 ] Zhijiang commented on FLINK-18238: -- The downstream task can receive the abort rpc call from

[jira] [Comment Edited] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135502#comment-17135502 ] Zhijiang edited comment on FLINK-18238 at 6/15/20, 6:56 AM: The downstream

[jira] [Closed] (FLINK-18089) Add the network zero-copy test into the azure E2E pipeline

[ https://issues.apache.org/jira/browse/FLINK-18089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-18089. Resolution: Fixed Master: bb2affbcb6ea748d5a8e8a4af188d4b6f21c1466 release-1.11: 

[jira] [Updated] (FLINK-18089) Add the network zero-copy test into the azure E2E pipeline

[ https://issues.apache.org/jira/browse/FLINK-18089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18089: - Affects Version/s: 1.11.0 > Add the network zero-copy test into the azure E2E pipeline >

[jira] [Updated] (FLINK-18089) Add the network zero-copy test into the azure E2E pipeline

[ https://issues.apache.org/jira/browse/FLINK-18089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-18089: - Fix Version/s: 1.12.0 > Add the network zero-copy test into the azure E2E pipeline >

[jira] [Commented] (FLINK-18238) RemoteChannelThroughputBenchmark deadlocks

[ https://issues.apache.org/jira/browse/FLINK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17135372#comment-17135372 ] Zhijiang commented on FLINK-18238: -- [~kevin.cyj] already finalized the root cause which was introduced

[jira] [Commented] (FLINK-17182) RemoteInputChannelTest.testConcurrentOnSenderBacklogAndRecycle fail on azure

[ https://issues.apache.org/jira/browse/FLINK-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132997#comment-17132997 ] Zhijiang commented on FLINK-17182: -- I think I should review this PR today to save some efforts for

[jira] [Commented] (FLINK-17869) Fix the race condition of aborting unaligned checkpoint

[ https://issues.apache.org/jira/browse/FLINK-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132873#comment-17132873 ] Zhijiang commented on FLINK-17869: -- Merged in release-1.11: 7bb3ffa91a9916348d2f0a6a2e6cba4b109be56e, 

[jira] [Closed] (FLINK-16821) Run Kubernetes test failed with invalid named "minikube"

[ https://issues.apache.org/jira/browse/FLINK-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang closed FLINK-16821. Resolution: Fixed > Run Kubernetes test failed with invalid named "minikube" >

[jira] [Commented] (FLINK-16821) Run Kubernetes test failed with invalid named "minikube"

[ https://issues.apache.org/jira/browse/FLINK-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132871#comment-17132871 ] Zhijiang commented on FLINK-16821: -- Thanks for the feedback. I have not found other failures after

[jira] [Updated] (FLINK-16821) Run Kubernetes test failed with invalid named "minikube"

[ https://issues.apache.org/jira/browse/FLINK-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang updated FLINK-16821: - Affects Version/s: 1.11.0 > Run Kubernetes test failed with invalid named "minikube" >

[jira] [Comment Edited] (FLINK-16821) Run Kubernetes test failed with invalid named "minikube"

[ https://issues.apache.org/jira/browse/FLINK-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130833#comment-17130833 ] Zhijiang edited comment on FLINK-16821 at 6/10/20, 4:05 PM: The same issue

[jira] [Commented] (FLINK-16821) Run Kubernetes test failed with invalid named "minikube"

[ https://issues.apache.org/jira/browse/FLINK-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130833#comment-17130833 ] Zhijiang commented on FLINK-16821: -- The same issue seems happen again in release-1.11 brancn:

[jira] [Reopened] (FLINK-16821) Run Kubernetes test failed with invalid named "minikube"

[ https://issues.apache.org/jira/browse/FLINK-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijiang reopened FLINK-16821: -- > Run Kubernetes test failed with invalid named "minikube" >

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