Closed andrewjstone closed 7 years ago
If no prior namespace was entered, it returns primary unknown
. This is also incorrect, as it doesn't indicate the namespace is unknown.
The fixed code now returns Primary unknown
when the primary can't be found. This is only a partial fix. I believe there shouldn't be a timeout at all. Instead, an error should be returned right away stating the namespace can't be found.
Reopening to look into why the code waits for a timeout at all.
Correct behavior:
andrewstone$ rlwrap target/debug/v2r2-cli-client 127.0.0.1:2002
v2r2> enter 2cc91edf-104b-4c60-9912-dd91116f3d50
Unknown namespace
v2r2> enter d604063d-92de-4e39-8f5a-49f9cb10f42b
Client registered. Primary = name: "r" group: "d604063d-92de-4e39-8f5a-49f9cb10f42b" node_name: "dev1" node_addr: "127.0.0.1:2000"
v2r2> enter 2cc91edf-104b-4c60-9912-dd91116f3d50
Unknown namespace
When attempting to "enter" a namespace that doesn't exist, the CLI hangs and will eventually timeout. However, instead of displaying
timeout
, it shows the primary for the last entered namespace.Below, the uuid ending in
39
exists, but40
does not.