Vishwas created IGNITE-13974:
--------------------------------
Summary: onDisconnected() method does not get called for
thinClient on "kubectl delete pod"
Key: IGNITE-13974
URL: https://issues.apache.org/jira/browse/IGNITE-13974
Project: Ignite
Issue Type: Bug
Components: jdbc, thin client
Affects Versions: 2.9
Environment: k8s
Reporter: Vishwas
Below is the test I am performing:
1) Bring up ignite on k8s cluster 2 pods of Ignite server are running.
2) Connect via sqlline to the Ignite Cluster (connect via k8s service):
{code:java}
./sqlline.sh --verbose=true -u
"jdbc:ignite:thin://ignite-service.ignite.svc.cluster.local:10800" -n test_user
-p test_user
{code}
3) Restart the pod on which sqlline connection is made
{code:java}
kubectl delete pod <THIN_CLIENT_CONNECTED_POD>
{code}
4) *Observation ClientListenerAbstractConnectionContext.onDisconnected() is not
getting called.*
*This causes leak of the authenticationContext as onSessionExpired method does
not get called.*
+Note:+
When I tried the same scenario on a windows machine, I did not hit the issue
and the onDisconnected() method is getting called.
For step 3 above, I connected to ignite visor and ran the kill -k command on
windows.
When I ran the same kill -k command on k8s cluster from visor, I do not see
this issue.
What should be the behaviour when "kubectl delete pod" is triggered ? I think
onDisconnected() should get called.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
