[jira] [Updated] (FLINK-32756) Reuse ClientHighAvailabilityServices when creating RestClusterClient

2023-12-13 Thread ASF GitHub Bot (Jira)


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

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

> Reuse ClientHighAvailabilityServices when creating RestClusterClient
> 
>
> Key: FLINK-32756
> URL: https://issues.apache.org/jira/browse/FLINK-32756
> Project: Flink
>  Issue Type: Sub-task
>  Components: Client / Job Submission
>Reporter: xiangyu feng
>Assignee: xiangyu feng
>Priority: Major
>  Labels: pull-request-available
>
> Currently, every newly built RestClusterClient will create a new 
> ClientHighAvailabilityServices which is both unnecessary and resource 
> consuming. For example, each ZooKeeperClientHAServices contains a ZKClient 
> which holds a connection to ZK server and several related threads.
> By reusing ClientHighAvailabilityServices across multiple RestClusterClient 
> instances, we can save system resources(threads, connections), connection 
> establish time and leader retrieval time.



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


[jira] [Updated] (FLINK-32756) Reuse ClientHighAvailabilityServices when creating RestClusterClient

2023-11-28 Thread xiangyu feng (Jira)


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

xiangyu feng updated FLINK-32756:
-
Parent: FLINK-33683
Issue Type: Sub-task  (was: Improvement)

> Reuse ClientHighAvailabilityServices when creating RestClusterClient
> 
>
> Key: FLINK-32756
> URL: https://issues.apache.org/jira/browse/FLINK-32756
> Project: Flink
>  Issue Type: Sub-task
>  Components: Client / Job Submission
>Reporter: xiangyu feng
>Assignee: xiangyu feng
>Priority: Major
>
> Currently, every newly built RestClusterClient will create a new 
> ClientHighAvailabilityServices which is both unnecessary and resource 
> consuming. For example, each ZooKeeperClientHAServices contains a ZKClient 
> which holds a connection to ZK server and several related threads.
> By reusing ClientHighAvailabilityServices across multiple RestClusterClient 
> instances, we can save system resources(threads, connections), connection 
> establish time and leader retrieval time.



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


[jira] [Updated] (FLINK-32756) Reuse ClientHighAvailabilityServices when creating RestClusterClient

2023-11-28 Thread xiangyu feng (Jira)


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

xiangyu feng updated FLINK-32756:
-
Parent: (was: FLINK-25318)
Issue Type: Improvement  (was: Sub-task)

> Reuse ClientHighAvailabilityServices when creating RestClusterClient
> 
>
> Key: FLINK-32756
> URL: https://issues.apache.org/jira/browse/FLINK-32756
> Project: Flink
>  Issue Type: Improvement
>  Components: Client / Job Submission
>Reporter: xiangyu feng
>Assignee: xiangyu feng
>Priority: Major
>
> Currently, every newly built RestClusterClient will create a new 
> ClientHighAvailabilityServices which is both unnecessary and resource 
> consuming. For example, each ZooKeeperClientHAServices contains a ZKClient 
> which holds a connection to ZK server and several related threads.
> By reusing ClientHighAvailabilityServices across multiple RestClusterClient 
> instances, we can save system resources(threads, connections), connection 
> establish time and leader retrieval time.



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


[jira] [Updated] (FLINK-32756) Reuse ClientHighAvailabilityServices when creating RestClusterClient

2023-11-28 Thread xiangyu feng (Jira)


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

xiangyu feng updated FLINK-32756:
-
Summary: Reuse ClientHighAvailabilityServices when creating 
RestClusterClient  (was: Reuse ClientHighAvailabilityServices in 
RestClusterClient when submitting OLAP jobs)

> Reuse ClientHighAvailabilityServices when creating RestClusterClient
> 
>
> Key: FLINK-32756
> URL: https://issues.apache.org/jira/browse/FLINK-32756
> Project: Flink
>  Issue Type: Sub-task
>  Components: Client / Job Submission
>Reporter: xiangyu feng
>Priority: Major
>
> Currently, every newly built RestClusterClient will create a new 
> ClientHighAvailabilityServices which is both unnecessary and resource 
> consuming. For example, each ZooKeeperClientHAServices contains a ZKClient 
> which holds a connection to ZK server and several related threads.
> By reusing ClientHighAvailabilityServices across multiple RestClusterClient 
> instances, we can save system resources(threads, connections), connection 
> establish time and leader retrieval time.



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