-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using AWS cluster - Trouble writing values to it #166
Comments
Do you mean a Redis cluster? So far there is not support for Redis-cluster in Boost.Redis. |
It is important to know what message is contained in that error. |
Can you please replace if (std::get<0>(resp).has_error()) {
std::cout << "Type: " << to_string(std::get<0>(resp).error().data_type) << std::endl;
std::cout << "Diagnostic: " << std::get<0>(resp).error().diagnostic << std::endl;
}
if (std::get<1>(resp).has_error()) {
std::cout << "Type: " << to_string(std::get<1>(resp).error().data_type) << std::endl;
std::cout << "Diagnostic: " << std::get<1>(resp).error().diagnostic << std::endl;
} Let me then know what diagnostic do you get. |
This is what the response now:
Where xxx-xxx-xxx is one of the cluster nodes |
Ok, this means you are using a Redis cluster. As I said above, Boost.Redis does not provide any facility for cluster setups. In this case you would have to deal with the redirect yourself as describe under the in MOVED Redirection, which means creating a new connection to that node and maintaining a map of connections to prevent from opening more than one connection to the same node. Feel free to open an issue to add Redis cluster support, however I can't give you an estimate about when I will come up with it. |
Hi,
Working on my app, everything looks fine in my local development environment with a single redis server on standard port. Running into problems when using an AWS environment with a cluster. Is there anything specific that needs to be set for a cluster?
The initial connection seems to go correctly using the following:
and I see the following on std::cout, so it seems the cluster was correctly identified:
However, when trying an HSET operation I got an exception:
Exception saving session to Redis. %s - keyid - Got RESP3 simple-error. [boost.redis:11]
This is the code that tries to write to the Cluster: (redisInst is an instance of sync_connection as it came from the examples dir)
The text was updated successfully, but these errors were encountered: