Skip to content
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 API gateway with a redis cluster #259

Closed
sayanh opened this issue Oct 13, 2017 · 3 comments
Closed

Using API gateway with a redis cluster #259

sayanh opened this issue Oct 13, 2017 · 3 comments

Comments

@sayanh
Copy link

sayanh commented Oct 13, 2017

Currently, api gateway works well with a single redis instance. But if we use a cluster of 3 redis instances, api gateway fails to work giving the following error:
wsk api list error: Unable to obtain the API list: Unable to obtain API(s) from the API Gateway (status code 500): {"status":500,"message":"Error: Failed to retrieve APIs: MOVED 2088 1.2.3.4:6379"}

@mhamann
Copy link
Member

mhamann commented Oct 27, 2017

@sayanh Pull requests are welcome :-)

Will at least need more details around what you are passing in, etc.

@sayanh
Copy link
Author

sayanh commented Nov 8, 2017

I think API gateway is quite impossible to work with redis cluster because of this open issue openresty/lua-resty-redis#102

Moreover, IMO, redis may not be the right tool for storing API information.

@mhamann
Copy link
Member

mhamann commented May 8, 2019

The recommended approach is to use redis replication and a proxy like twemproxy to handle connecting to the appropriate number of members (also enables sharding, hashing, etc if desired).

Closing this issue.

@mhamann mhamann closed this as completed May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants