[jira] [Commented] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

[ https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408576#comment-17408576 ] Aitozi commented on FLINK-24063: [~wangyang0918] IMO If the {{clusterComponent#shutDownFuture}}

[jira] [Created] (FLINK-24117) Remove unHandledErrorListener in ZooKeeperLeaderElectionDriver and ZooKeeperLeaderRetrievalDriver

Aitozi created FLINK-24117: -- Summary: Remove unHandledErrorListener in ZooKeeperLeaderElectionDriver and ZooKeeperLeaderRetrievalDriver Key: FLINK-24117 URL: https://issues.apache.org/jira/browse/FLINK-24117

[jira] [Commented] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

[ https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408072#comment-17408072 ] Aitozi commented on FLINK-24063: [~trohrmann] I also meant to change the 

[jira] [Commented] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

[ https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407945#comment-17407945 ] Aitozi commented on FLINK-24063: Hi [~wangyang0918] I truly mean the  {{STOP_APPLICATION}} in the 

[jira] [Commented] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

[ https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407933#comment-17407933 ] Aitozi commented on FLINK-24063: Thanks for your reply [~trohrmann]. I think there are two case will

[jira] [Comment Edited] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

[ https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407082#comment-17407082 ] Aitozi edited comment on FLINK-24063 at 8/31/21, 5:40 AM: -- Looking forward to

[jira] [Commented] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

[ https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407082#comment-17407082 ] Aitozi commented on FLINK-24063: Looking forward to your opinion on this [~trohrmann] > Reconsider the

[jira] [Updated] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

[ https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-24063: --- Description: If the job runCluster failed, it will trigger the STOP_APPLICATION behavior. But if we

[jira] [Created] (FLINK-24063) Reconsider the behavior of ClusterEntrypoint#startCluster failure handler

Aitozi created FLINK-24063: -- Summary: Reconsider the behavior of ClusterEntrypoint#startCluster failure handler Key: FLINK-24063 URL: https://issues.apache.org/jira/browse/FLINK-24063 Project: Flink

[jira] [Created] (FLINK-24060) Move ZooKeeperUtilTest to right place

Aitozi created FLINK-24060: -- Summary: Move ZooKeeperUtilTest to right place Key: FLINK-24060 URL: https://issues.apache.org/jira/browse/FLINK-24060 Project: Flink Issue Type: Technical Debt

[jira] [Updated] (FLINK-24056) Remove unused ZooKeeperUtilityFactory and clean up ZooKeeperUtilTest

[ https://issues.apache.org/jira/browse/FLINK-24056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-24056: --- Summary: Remove unused ZooKeeperUtilityFactory and clean up ZooKeeperUtilTest (was: Remove unused

[jira] [Created] (FLINK-24056) Remove unused ZooKeeperUtilityFactory

Aitozi created FLINK-24056: -- Summary: Remove unused ZooKeeperUtilityFactory Key: FLINK-24056 URL: https://issues.apache.org/jira/browse/FLINK-24056 Project: Flink Issue Type: Bug

[jira] [Updated] (FLINK-24021) Potential job unrecoverable due to Network failure

[ https://issues.apache.org/jira/browse/FLINK-24021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-24021: --- Description: Now we use zk to do leader election and retrieval for HA. And we register a fatalError

[jira] [Commented] (FLINK-24021) Potential job unrecoverable due to Network failure

[ https://issues.apache.org/jira/browse/FLINK-24021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406723#comment-17406723 ] Aitozi commented on FLINK-24021: I have create a fix [PR|https://github.com/apache/flink/pull/17053] ,

[jira] [Commented] (FLINK-24021) Potential job unrecoverable due to Network failure

[ https://issues.apache.org/jira/browse/FLINK-24021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405674#comment-17405674 ] Aitozi commented on FLINK-24021: cc [~trohrm...@apache.org] > Potential job unrecoverable due to

[jira] [Created] (FLINK-24021) Potential job unrecoverable due to Network failure

Aitozi created FLINK-24021: -- Summary: Potential job unrecoverable due to Network failure Key: FLINK-24021 URL: https://issues.apache.org/jira/browse/FLINK-24021 Project: Flink Issue Type: Bug

[jira] [Commented] (FLINK-23871) Dispatcher should handle finishing job exception when recover

[ https://issues.apache.org/jira/browse/FLINK-23871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401580#comment-17401580 ] Aitozi commented on FLINK-23871: cc [~trohrmann] > Dispatcher should handle finishing job exception

[jira] [Updated] (FLINK-23871) Dispatcher should handle finishing job exception when recover

[ https://issues.apache.org/jira/browse/FLINK-23871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-23871: --- Description: The exception during run recovery job will trigger fatal error which is introduced in

[jira] [Created] (FLINK-23871) Dispatcher should handle finishing job exception when recover

Aitozi created FLINK-23871: -- Summary: Dispatcher should handle finishing job exception when recover Key: FLINK-23871 URL: https://issues.apache.org/jira/browse/FLINK-23871 Project: Flink Issue

[jira] [Commented] (FLINK-23415) Shade kryo library to reduce class conflict

[ https://issues.apache.org/jira/browse/FLINK-23415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398034#comment-17398034 ] Aitozi commented on FLINK-23415: Get it, thanks for explanation.  > Shade kryo library to reduce class

[jira] [Commented] (FLINK-23031) Support to emit window result with periodic or non_periodic

[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17391552#comment-17391552 ] Aitozi commented on FLINK-23031: ping [~jark] > Support to emit window result with periodic or

[jira] [Commented] (FLINK-23415) Shade kryo library to reduce class conflict

[ https://issues.apache.org/jira/browse/FLINK-23415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385478#comment-17385478 ] Aitozi commented on FLINK-23415: Do you mean that user may have dependency with Kryo in flink binary ? 

[jira] [Comment Edited] (FLINK-23031) Support to emit window result with periodic or non_periodic

[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385188#comment-17385188 ] Aitozi edited comment on FLINK-23031 at 7/22/21, 5:21 AM: -- Hi [~jark] , after

[jira] [Commented] (FLINK-23415) Shade kryo library to reduce class conflict

[ https://issues.apache.org/jira/browse/FLINK-23415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385259#comment-17385259 ] Aitozi commented on FLINK-23415: Hi [~chesnay] , do you have any suggestion on this ? > Shade kryo

[jira] [Comment Edited] (FLINK-23031) Support to emit window result with periodic or non_periodic

[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385188#comment-17385188 ] Aitozi edited comment on FLINK-23031 at 7/22/21, 2:02 AM: -- Hi [~jark] , after

[jira] [Commented] (FLINK-23031) Support to emit window result with periodic or non_periodic

[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385188#comment-17385188 ] Aitozi commented on FLINK-23031: Hi [~jark] , after some offline discussion with you. I rethink this

[jira] [Updated] (FLINK-23415) Shade kryo library to reduce class conflict

[ https://issues.apache.org/jira/browse/FLINK-23415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-23415: --- Component/s: BuildSystem / Shaded > Shade kryo library to reduce class conflict >

[jira] [Commented] (FLINK-23181) Add support for multi hop window

[ https://issues.apache.org/jira/browse/FLINK-23181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383404#comment-17383404 ] Aitozi commented on FLINK-23181: Thanks [~lzljs3620320] for your inputs. I think it's a good idea. I

[jira] [Commented] (FLINK-22594) Report oom killed pod in k8s resource manager

[ https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383396#comment-17383396 ] Aitozi commented on FLINK-22594: I have create the pull request to implement this , could you help to

[jira] [Commented] (FLINK-22594) Report oom killed pod in k8s resource manager

[ https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382460#comment-17382460 ] Aitozi commented on FLINK-22594: As far as i know , the OOMKilled metrics may be only available from k8s

[jira] [Created] (FLINK-23415) Shade kryo library to reduce class conflict

Aitozi created FLINK-23415: -- Summary: Shade kryo library to reduce class conflict Key: FLINK-23415 URL: https://issues.apache.org/jira/browse/FLINK-23415 Project: Flink Issue Type: Improvement

[jira] [Commented] (FLINK-22594) Report oom killed pod in k8s resource manager

[ https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371494#comment-17371494 ] Aitozi commented on FLINK-22594: Agree with you that we can move some logic to a k8s operator. But I

[jira] [Commented] (FLINK-23163) Add debug ability for kubernetes client

[ https://issues.apache.org/jira/browse/FLINK-23163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371478#comment-17371478 ] Aitozi commented on FLINK-23163: I think it could be helpful when we have to determine the behavior of

[jira] [Commented] (FLINK-23181) Add support for multi hop window

[ https://issues.apache.org/jira/browse/FLINK-23181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371450#comment-17371450 ] Aitozi commented on FLINK-23181: Thanks [~jark] for looking at this. This issue is meant to add an

[jira] [Commented] (FLINK-23179) Support PIVOT and UNPIVOT

[ https://issues.apache.org/jira/browse/FLINK-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371219#comment-17371219 ] Aitozi commented on FLINK-23179: Big+1 [~lzljs3620320] Is there any plan for the support of pivot

[jira] [Created] (FLINK-23181) Add support for multi hop window

Aitozi created FLINK-23181: -- Summary: Add support for multi hop window Key: FLINK-23181 URL: https://issues.apache.org/jira/browse/FLINK-23181 Project: Flink Issue Type: New Feature

[jira] [Updated] (FLINK-23163) Add debug ability for kubernetes client

[ https://issues.apache.org/jira/browse/FLINK-23163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-23163: --- Description: add option to enable http client debug log (was: # set user agent to http client # add

[jira] [Created] (FLINK-23163) Add debug ability for kubernetes client

Aitozi created FLINK-23163: -- Summary: Add debug ability for kubernetes client Key: FLINK-23163 URL: https://issues.apache.org/jira/browse/FLINK-23163 Project: Flink Issue Type: Improvement

[jira] [Commented] (FLINK-22594) Report oom killed pod in k8s resource manager

[ https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370162#comment-17370162 ] Aitozi commented on FLINK-22594: Thanks [~fly_in_gis] for pointing that , But I think report the oom

[jira] [Commented] (FLINK-22594) Report oom killed pod in k8s resource manager

[ https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365892#comment-17365892 ] Aitozi commented on FLINK-22594: I have made an implementation for this issue, could you help review

[jira] [Commented] (FLINK-23031) Support to emit window result with periodic or non_periodic

[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365841#comment-17365841 ] Aitozi commented on FLINK-23031: I have made a implementation , could you help take a look  [~jark] ? In

[jira] [Commented] (FLINK-23031) Support to emit window result with periodic or non_periodic

[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365545#comment-17365545 ] Aitozi commented on FLINK-23031: [~jark] I think we can avoid to register new timer in 

[jira] [Commented] (FLINK-23031) Support to emit window result with periodic or non_periodic

[ https://issues.apache.org/jira/browse/FLINK-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17365306#comment-17365306 ] Aitozi commented on FLINK-23031: In flink sql, we can use EmitStrategy to set an early or late trigger

[jira] [Created] (FLINK-23031) Support to emit window result with periodic or non_periodic

Aitozi created FLINK-23031: -- Summary: Support to emit window result with periodic or non_periodic Key: FLINK-23031 URL: https://issues.apache.org/jira/browse/FLINK-23031 Project: Flink Issue Type:

[jira] [Commented] (FLINK-22594) Report oom killed pod in k8s resource manager

[ https://issues.apache.org/jira/browse/FLINK-22594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17340766#comment-17340766 ] Aitozi commented on FLINK-22594: If container oom killed due to run out of memory, the container status

[jira] [Created] (FLINK-22594) Report oom killed pod in k8s resource manager

Aitozi created FLINK-22594: -- Summary: Report oom killed pod in k8s resource manager Key: FLINK-22594 URL: https://issues.apache.org/jira/browse/FLINK-22594 Project: Flink Issue Type: Improvement

[jira] [Commented] (FLINK-20830) Add a type of HEADLESS_CLUSTER_IP for rest service type

[ https://issues.apache.org/jira/browse/FLINK-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17301544#comment-17301544 ] Aitozi commented on FLINK-20830: It seems has performance problem when cluster scale is large when proxy

[jira] [Updated] (FLINK-20830) Add a type of HEADLESS_CLUSTER_IP for rest service type

[ https://issues.apache.org/jira/browse/FLINK-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-20830: --- Description: Now we can choose ClusterIP or NodePort or LoadBalancer as rest service type. But in our

[jira] [Created] (FLINK-20830) Add a type of HEADLESS_CLUSTER_IP for rest service type

Aitozi created FLINK-20830: -- Summary: Add a type of HEADLESS_CLUSTER_IP for rest service type Key: FLINK-20830 URL: https://issues.apache.org/jira/browse/FLINK-20830 Project: Flink Issue Type:

[jira] [Commented] (FLINK-20411) The annotation config do not support complex structure

[ https://issues.apache.org/jira/browse/FLINK-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17240747#comment-17240747 ] Aitozi commented on FLINK-20411: Got it, thanks for your explanation > The annotation config do not

[jira] [Commented] (FLINK-20411) The annotation config do not support complex structure

[ https://issues.apache.org/jira/browse/FLINK-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17240188#comment-17240188 ] Aitozi commented on FLINK-20411: If we accept the new config, the old config can be replace by the new

[jira] [Updated] (FLINK-20411) The annotation config do not support complex structure

[ https://issues.apache.org/jira/browse/FLINK-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-20411: --- Description: Now we support user to set annotations by these config, the format is "k1:v1,k2:v2". #

[jira] [Updated] (FLINK-20411) The annotation config do not support complex structure

[ https://issues.apache.org/jira/browse/FLINK-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-20411: --- Description: Now we support user to set annotations by these config, the format is "k1:v1,k2:v2". #

[jira] [Created] (FLINK-20411) The annotation config do not support complex structure

Aitozi created FLINK-20411: -- Summary: The annotation config do not support complex structure Key: FLINK-20411 URL: https://issues.apache.org/jira/browse/FLINK-20411 Project: Flink Issue Type:

[jira] [Commented] (FLINK-16142) Memory Leak causes Metaspace OOM error on repeated job submission

[ https://issues.apache.org/jira/browse/FLINK-16142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096342#comment-17096342 ] Aitozi commented on FLINK-16142: Hi，[~sewen] as  you said , the class can not be released by

[jira] [Commented] (FLINK-13771) Support kqueue Netty transports (MacOS)

[ https://issues.apache.org/jira/browse/FLINK-13771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922939#comment-16922939 ] Aitozi commented on FLINK-13771: Hi [~NicoK], is this work in progress? can i do a try on this issue? >

[jira] [Commented] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878996#comment-16878996 ] Aitozi commented on FLINK-12852: Thanks [~gaoyunhaii] for your explanation, I think over this today,

[jira] [Comment Edited] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878727#comment-16878727 ] Aitozi edited comment on FLINK-12852 at 7/4/19 3:09 PM: [~zjwang] I'am sorry

[jira] [Comment Edited] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878727#comment-16878727 ] Aitozi edited comment on FLINK-12852 at 7/4/19 3:09 PM: [~zjwang] I'am sorry

[jira] [Comment Edited] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878727#comment-16878727 ] Aitozi edited comment on FLINK-12852 at 7/4/19 3:03 PM: [~zjwang] I'am sorry

[jira] [Comment Edited] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878727#comment-16878727 ] Aitozi edited comment on FLINK-12852 at 7/4/19 3:03 PM: [~zjwang] I'am sorry

[jira] [Comment Edited] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878727#comment-16878727 ] Aitozi edited comment on FLINK-12852 at 7/4/19 3:00 PM: [~zjwang] My mean is

[jira] [Commented] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878727#comment-16878727 ] Aitozi commented on FLINK-12852: [~zjwang] My mean is that _numTotalRequiredBuffers_ is not calculated

[jira] [Commented] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878609#comment-16878609 ] Aitozi commented on FLINK-12852: Hi， [~gaoyunhaii][~zjwang] I check the allocation logic again, I found

[jira] [Comment Edited] (FLINK-12852) Deadlock occurs when requiring exclusive buffer for RemoteInputChannel

[ https://issues.apache.org/jira/browse/FLINK-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878609#comment-16878609 ] Aitozi edited comment on FLINK-12852 at 7/4/19 12:26 PM: - Hi， [~gaoyunhaii]

[jira] [Commented] (FLINK-13013) Make sure that SingleInputGate can always request partitions

[ https://issues.apache.org/jira/browse/FLINK-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876272#comment-16876272 ] Aitozi commented on FLINK-13013: A little question here: The first data fetch will request subpartition

[jira] [Commented] (FLINK-12859) ClassNotFoundException during MapRFs init

[ https://issues.apache.org/jira/browse/FLINK-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864926#comment-16864926 ] Aitozi commented on FLINK-12859: [~yunta] I repost the image. Do you have any idea about this ? >

[jira] [Updated] (FLINK-12859) ClassNotFoundException during MapRFs init

[ https://issues.apache.org/jira/browse/FLINK-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-12859: --- Attachment: 20190616110004.jpg > ClassNotFoundException during MapRFs init >

[jira] [Created] (FLINK-12859) ClassNotFoundException during MapRFs init

Aitozi created FLINK-12859: -- Summary: ClassNotFoundException during MapRFs init Key: FLINK-12859 URL: https://issues.apache.org/jira/browse/FLINK-12859 Project: Flink Issue Type: Test

[jira] [Assigned] (FLINK-12669) Implement FixedDelayRestartBackoffTimeStrategy

[ https://issues.apache.org/jira/browse/FLINK-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi reassigned FLINK-12669: -- Assignee: BoWang (was: Aitozi) > Implement FixedDelayRestartBackoffTimeStrategy >

[jira] [Commented] (FLINK-12669) Implement FixedDelayRestartBackoffTimeStrategy

[ https://issues.apache.org/jira/browse/FLINK-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861134#comment-16861134 ] Aitozi commented on FLINK-12669: OK, I was blocking with another issue, sorry for delaying your work

[jira] [Commented] (FLINK-12669) Implement FixedDelayRestartBackoffTimeStrategy

[ https://issues.apache.org/jira/browse/FLINK-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853750#comment-16853750 ] aitozi commented on FLINK-12669: ok, thanks for remind, i will check that issue [~till.rohrmann] >

[jira] [Commented] (FLINK-12669) Implement FixedDelayRestartBackoffTimeStrategy

[ https://issues.apache.org/jira/browse/FLINK-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850744#comment-16850744 ] aitozi commented on FLINK-12669: I will try to implement this subtask [~till.rohrmann] > Implement

[jira] [Assigned] (FLINK-12669) Implement FixedDelayRestartBackoffTimeStrategy

[ https://issues.apache.org/jira/browse/FLINK-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi reassigned FLINK-12669: -- Assignee: aitozi > Implement FixedDelayRestartBackoffTimeStrategy >

[jira] [Commented] (FLINK-12653) Keyed state backend fails to restore during rescaling

[ https://issues.apache.org/jira/browse/FLINK-12653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849932#comment-16849932 ] aitozi commented on FLINK-12653: Thanks for the detail information, I will try look into this problem.

[jira] [Commented] (FLINK-12576) inputQueueLength metric does not work for LocalInputChannels

[ https://issues.apache.org/jira/browse/FLINK-12576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849862#comment-16849862 ] aitozi commented on FLINK-12576: Hi, [~pnowojski] I check the code, for localInputChannel do we just

[jira] [Commented] (FLINK-10121) Introduce methods to remove registered operator states

[ https://issues.apache.org/jira/browse/FLINK-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849087#comment-16849087 ] aitozi commented on FLINK-10121: Hi,[~srichter] Is this still ongoing work ? I think it's a valuable

[jira] [Commented] (FLINK-10098) Programmatically select timer storage backend

[ https://issues.apache.org/jira/browse/FLINK-10098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849082#comment-16849082 ] aitozi commented on FLINK-10098: I will work on this issue to solve the problem > Programmatically

[jira] [Assigned] (FLINK-10098) Programmatically select timer storage backend

[ https://issues.apache.org/jira/browse/FLINK-10098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi reassigned FLINK-10098: -- Assignee: aitozi > Programmatically select timer storage backend >

[jira] [Updated] (FLINK-12637) Add floatingBufferUsage and exclusiveBufferUsage for credit based mode

[ https://issues.apache.org/jira/browse/FLINK-12637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi updated FLINK-12637: --- Description: Described [here|https://github.com/apache/flink/pull/8455#issuecomment-496077999] (was:

[jira] [Created] (FLINK-12637) Add floatingBufferUsage and exclusiveBufferUsage for credit based mode

aitozi created FLINK-12637: -- Summary: Add floatingBufferUsage and exclusiveBufferUsage for credit based mode Key: FLINK-12637 URL: https://issues.apache.org/jira/browse/FLINK-12637 Project: Flink

[jira] [Commented] (FLINK-12297) Clean the closure for OutputTags in PatternStream

[ https://issues.apache.org/jira/browse/FLINK-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848002#comment-16848002 ] aitozi commented on FLINK-12297: Hi，[~aljoscha] Since you have noticed this issue, can you take a look

[jira] [Assigned] (FLINK-12576) inputQueueLength metric does not work for LocalInputChannels

[ https://issues.apache.org/jira/browse/FLINK-12576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi reassigned FLINK-12576: -- Assignee: aitozi > inputQueueLength metric does not work for LocalInputChannels >

[jira] [Assigned] (FLINK-11193) rockdb customize configuration Covered by jobmaster

[ https://issues.apache.org/jira/browse/FLINK-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi reassigned FLINK-11193: -- Assignee: aitozi > rockdb customize configuration Covered by jobmaster >

[jira] [Commented] (FLINK-11193) rockdb customize configuration Covered by jobmaster

[ https://issues.apache.org/jira/browse/FLINK-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840553#comment-16840553 ] aitozi commented on FLINK-11193: It's truly a bug, I will try to drive the fix. > rockdb customize

[jira] [Commented] (FLINK-12284) InputBufferPoolUsage is incorrect in credit-based network control flow

[ https://issues.apache.org/jira/browse/FLINK-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840499#comment-16840499 ] aitozi commented on FLINK-12284: It's truly a bug, because the exclusive buffers are assigned in advance

[jira] [Assigned] (FLINK-12284) InputBufferPoolUsage is incorrect in credit-based network control flow

[ https://issues.apache.org/jira/browse/FLINK-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi reassigned FLINK-12284: -- Assignee: aitozi > InputBufferPoolUsage is incorrect in credit-based network control flow >

[jira] [Commented] (FLINK-9431) Introduce TimeEnd State to flink cep

[ https://issues.apache.org/jira/browse/FLINK-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840097#comment-16840097 ] aitozi commented on FLINK-9431: --- Thanks for your feedback [~dawidwys], I will think over this feature

[jira] [Commented] (FLINK-12481) Make processing time timer trigger run via the mailbox

[ https://issues.apache.org/jira/browse/FLINK-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838457#comment-16838457 ] aitozi commented on FLINK-12481: OK，thanks for your reply. Looking forward it. :) > Make processing

[jira] [Commented] (FLINK-12498) java.io.IOException: Failed to fetch BLOB

[ https://issues.apache.org/jira/browse/FLINK-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838402#comment-16838402 ] aitozi commented on FLINK-12498: The exception stack shows that "too many open files", It may caused by

[jira] [Commented] (FLINK-12486) RocksDB State Backend docs don't explain that operator state is kept on heap

[ https://issues.apache.org/jira/browse/FLINK-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838372#comment-16838372 ] aitozi commented on FLINK-12486: I can do this a favour to complete the explanation. > RocksDB State

[jira] [Assigned] (FLINK-12486) RocksDB State Backend docs don't explain that operator state is kept on heap

[ https://issues.apache.org/jira/browse/FLINK-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi reassigned FLINK-12486: -- Assignee: aitozi > RocksDB State Backend docs don't explain that operator state is kept on heap >

[jira] [Commented] (FLINK-12481) Make processing time timer trigger run via the mailbox

[ https://issues.apache.org/jira/browse/FLINK-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838280#comment-16838280 ] aitozi commented on FLINK-12481: Hi, [~srichter] After going through the doc of this feature, I think it

[jira] [Created] (FLINK-12492) Minor optimize the cep operator by avoiding unnecessary copy

aitozi created FLINK-12492: -- Summary: Minor optimize the cep operator by avoiding unnecessary copy Key: FLINK-12492 URL: https://issues.apache.org/jira/browse/FLINK-12492 Project: Flink Issue

[jira] [Commented] (FLINK-12351) AsyncWaitOperator should deep copy StreamElement when object reuse is enabled

[ https://issues.apache.org/jira/browse/FLINK-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827861#comment-16827861 ] aitozi commented on FLINK-12351: Hi, [~jark] I checked the objectuse config in other operator just now.

[jira] [Assigned] (FLINK-12297) Clean the closure for OutputTags in PatternStream

[ https://issues.apache.org/jira/browse/FLINK-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aitozi reassigned FLINK-12297: -- Assignee: aitozi > Clean the closure for OutputTags in PatternStream >

[jira] [Commented] (FLINK-12297) Clean the closure for OutputTags in PatternStream

[ https://issues.apache.org/jira/browse/FLINK-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824899#comment-16824899 ] aitozi commented on FLINK-12297: Hi, [~SleePy][~dawidwys] As I mentioned in

[jira] [Commented] (FLINK-12113) User code passing to fromCollection(Iterator, Class) not cleaned

[ https://issues.apache.org/jira/browse/FLINK-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824898#comment-16824898 ] aitozi commented on FLINK-12113: Can we enable the recursive clean in ClosureCleaner#clean by check the

[jira] [Commented] (FLINK-11912) Expose per partition Kafka lag metric in Flink Kafka connector

[ https://issues.apache.org/jira/browse/FLINK-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809641#comment-16809641 ] aitozi commented on FLINK-11912: Got it [~suez1224] . Thanks for your explanation, I think you are

[jira] [Commented] (FLINK-11912) Expose per partition Kafka lag metric in Flink Kafka connector

[ https://issues.apache.org/jira/browse/FLINK-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808541#comment-16808541 ] aitozi commented on FLINK-11912: Hi [~suez1224] , [~tzulitai] I have tried to solve this bug in a very

<    2   3   4   5   6   7   8   9   >