Back to bug 1027311
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Martin Gencur | 2013-11-06 16:13:01 UTC | Doc Text | Cause: The C++ HotRod client has a hard-coded level of intelligence (level 1). Consequence: The client has only basic intelligence which means it is not topology aware. Thus, when the client connects to a cluster, and servers join or leave the cluster, the client will not be aware of it. Workaround: When new nodes join the cluster or leave it while the C++ client is connected, make sure you restart all the clients to get the new view of the cluster. Another option is to make sure no servers leave or join the cluster during the session. Result: |
|
| Martin Gencur | 2013-12-10 13:17:32 UTC | CC | gsheldon | |
| Doc Text | Cause: The C++ HotRod client has a hard-coded level of intelligence (level 1). Consequence: The client has only basic intelligence which means it is not topology aware. Thus, when the client connects to a cluster, and servers join or leave the cluster | The C++ HotRod client has a hard-coded level of intelligence (level 1). As a result, the client has only basic intelligence, which means it is not topology aware. Thus, when the client connects to a cluster, and servers join or leave the cluster | ||
| Doc Text | , the client will not be aware of it. Workaround: When new nodes join the cluster or leave it while the C++ client is connected | , the client will not be aware of it. </para> <para> As a workaround, when new nodes join the cluster or leave it while the C++ client is connected | ||
| Doc Text | , make sure you restart all the clients to get the new view of the cluster. Another option is to make sure no servers leave or join the cluster during the session. Result: | , ensure all clients are restarted to get the new view of the cluster. Another option is to make sure no servers leave or join the cluster during the session. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Status | NEW | ON_QA | ||
| Target Release | --- | 6.2.0 | ||
| Target Milestone | --- | ER5 | ||
| Radim Vansa | 2013-12-10 13:25:20 UTC | Status | ON_QA | VERIFIED |
| Divya Mehra | 2014-01-10 04:55:30 UTC | Doc Text | The C++ HotRod client has a hard-coded level of intelligence (level 1). As a result, the client has only basic intelligence, which means it is not topology aware. Thus, when the client connects to a cluster, and servers join or leave the cluster | The C++ Hot Rod client has a hard-coded level of intelligence (level 1). As a result, the client has only basic intelligence, which means it is not topology aware. Thus, when the client connects to a cluster, and servers join or leave the cluster |
| Doc Text | , the client will not be aware of it. </para> <para> As a workaround, when new nodes join the cluster or leave it while the C++ client is connected | , the client will not be aware of it. </para> <para> As a workaround, when new nodes join the cluster or leave it while the C++ client is connected | ||
| Doc Text | , ensure all clients are restarted to get the new view of the cluster. Another option is to make sure no servers leave or join the cluster during the session. | , ensure all clients are restarted to get the new view of the cluster. Another option is to make sure no servers leave or join the cluster during the session. | ||
| Status | VERIFIED | ON_QA | ||
| Martin Gencur | 2014-01-10 08:01:33 UTC | Status | ON_QA | VERIFIED |
| John Skeoch | 2014-11-30 21:16:06 UTC | CC | mmarkus | sjacobs |
| PnT Account Manager | 2018-01-30 01:43:06 UTC | CC | dmehra | |
| PnT Account Manager | 2018-09-12 22:21:38 UTC | CC | gsheldon |
Back to bug 1027311