[jira] [Updated] (GEODE-10349) Client connects to a new server socket should check its availability

2022-06-02 Thread Anilkumar Gingade (Jira)


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

Anilkumar Gingade updated GEODE-10349:
--
Labels: pull-request-available  (was: needsTriage pull-request-available)

> Client connects to a new server socket should check its availability 
> -
>
> Key: GEODE-10349
> URL: https://issues.apache.org/jira/browse/GEODE-10349
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Xiaojian Zhou
>Assignee: Xiaojian Zhou
>Priority: Major
>  Labels: pull-request-available
>
> When client connects to a new server (or restarted server), it might 
> encounter SocketTimeoutException which could take 59 seconds. 
> To speed up, the idea is to check if the server address's is reachable with 
> smaller timeout. 
> If the server's address is not reachable, no need to block waiting for 59 
> seconds (DEFAULT_SOCKET_CONNECT_TIMEOUT). 



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


[jira] [Updated] (GEODE-10349) Client connects to a new server socket should check its availability

2022-06-01 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated GEODE-10349:
---
Labels: needsTriage pull-request-available  (was: needsTriage)

> Client connects to a new server socket should check its availability 
> -
>
> Key: GEODE-10349
> URL: https://issues.apache.org/jira/browse/GEODE-10349
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Xiaojian Zhou
>Priority: Major
>  Labels: needsTriage, pull-request-available
>
> When client connects to a new server (or restarted server), it might 
> encounter SocketTimeoutException which could take 59 seconds. 
> To speed up, the idea is to check if the server address's is reachable with 
> smaller timeout. 
> If the server's address is not reachable, no need to block waiting for 59 
> seconds (DEFAULT_SOCKET_CONNECT_TIMEOUT). 



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


[jira] [Updated] (GEODE-10349) Client connects to a new server socket should check its availability

2022-06-01 Thread Alexander Murmann (Jira)


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

Alexander Murmann updated GEODE-10349:
--
Labels: needsTriage  (was: )

> Client connects to a new server socket should check its availability 
> -
>
> Key: GEODE-10349
> URL: https://issues.apache.org/jira/browse/GEODE-10349
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Xiaojian Zhou
>Priority: Major
>  Labels: needsTriage
>
> When client connects to a new server (or restarted server), it might 
> encounter SocketTimeoutException which could take 59 seconds. 
> To speed up, the idea is to check if the server address's is reachable with 
> smaller timeout. 
> If the server's address is not reachable, no need to block waiting for 59 
> seconds (DEFAULT_SOCKET_CONNECT_TIMEOUT). 



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