[jira] [Resolved] (GEODE-10020) Improving LiveServerPinger logic

2022-06-28 Thread Mario Ivanac (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mario Ivanac resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Geode /  GEODE-10020  
 
 
  Improving LiveServerPinger logic   
 

  
 
 
 
 

 
Change By: 
 Mario Ivanac  
 
 
Fix Version/s: 
 1.16.0  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Reopened Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[jira] [Resolved] (GEODE-10020) Improving LiveServerPinger logic

2022-05-24 Thread Mario Ivanac (Jira) 


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

Mario Ivanac resolved GEODE-10020.
--
Fix Version/s: 1.16.0
   Resolution: Fixed

> Improving LiveServerPinger logic
> 
>
> Key: GEODE-10020
> URL: https://issues.apache.org/jira/browse/GEODE-10020
> Project: Geode
>  Issue Type: Improvement
>  Components: wan
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.16.0
>
>
> _When several gateway receivers have the same value for hostname-for-senders 
> (for example when running Geode under kubernetes and a load balancer balances 
> the load among the remote servers), it has been observed that number of 
> connections in GW senders pool used for sending ping message is much greater 
> then number of dispatcher threads, although in this case only one connection 
> could be used_ _(since destinations have same address and port )._
>  
> _For details see RFC._



--
This message was sent by Atlassian Jira
(v8.20.7#820007)