Hi, Recently in one of our client application for geode we are getting below exception.
Pool unexpected socket timed out on client Server unreachable: could not connect after 1 attempts After looking at various threads came to know that we need to set read-timeout in client configuration to a higher value.Default is 10 seconds I believe. Just curious to know why server would take more than 10 seconds to respond. As 10 seconds seems to be on a higher side already.For now we will probably increase to 30 seconds atleast and observe it if makes any difference. Also on the server side could see below warnings. ClientHealthMonitor Unregistering client with member id identity xxxx due to: Socket closed. Monitoring client with member id identity xxxx It had been 60534 ms since the latest heartbeat. Max interval is 60000. Terminated client. Could this be because of high load on a particular server? But we have seen these warnings on all of our data nodes. Any parameters we need to tune in server side for this? Thanks, Ashish
