You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* To verify the first point, set up a redis cluster following the updated readme and connect from the UI.
5
+
* Once connected, you should be able to send commands and recieve response from cluster like this:
6
+
```
7
+
> get foo
8
+
(nil)
9
+
> set foo bar
10
+
Ok
11
+
> get foo
12
+
bar
13
+
```
14
+
#1.1 And in the connect endpoint, when the connection with id already exists, you should also check if the properties (e.g. host name, port, cluster etc...) are changed or not. If changed, disconnect the old one and reconnect.
15
+
16
+
* To verify this, manually edit the localStorage, refresh the page and try to connect.
17
+
18
+
#2 Add a disconnect endpoint to the backend.
19
+
20
+
* This is implemented and integrated with the disconnect button above the instance info
21
+
22
+
#3 To verify if the backend removes the cache,
23
+
* run the server in dev mode (using ndb is recommended for running in debug mode) put a breakpoint in reconnecting callback in redis.js.
24
+
* set MAX_RETRIES in config/default.js.
25
+
26
+
#3.1 To verify idle timeout
27
+
* set a very low value (say 1) in the config/default.js > IDLE_TIMEOUT_IN_MINS variable.
28
+
* wait for 1 minute and run `get foo` from the UI. This will fail unless you manually reconnected in the meantime.
0 commit comments