Details
-
Improvement
-
Resolution: Fixed
-
Major
-
4.0.0
-
Security Level: Public
Description
Screen capture of issue is attached. Log files here:
http://customers.couchbase.com.s3.amazonaws.com/davidH/node1.zip
http://customers.couchbase.com.s3.amazonaws.com/davidH/node3.zip
http://customers.couchbase.com.s3.amazonaws.com/davidH/node2.zip
Created a 3 node sherlock cluster (build 1891).
For 2 different reasons, the UI automatically took me back to the login prompt:
(1) UI logged me out after being idle for a period of time
(2) After successfully logging back in, the UI immediately reported it could not communicate with the cluster. This was then followed by an automatic log-out which sent me back to the login prompt (see screen capture).
A more typical approach when automatically logging customers out is to either take them to a page or pop-up a dialog saying they have been timed out (either due to inactivity or inability to communicate with the cluster). (2) is the greater concern because it can lead to a "let me try that again" loop and it is not apparent that the cluster is under distress.