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

decache rdir entry after reassign #1192

Open
jkasarherou opened this issue Oct 2, 2017 · 3 comments
Open

decache rdir entry after reassign #1192

jkasarherou opened this issue Oct 2, 2017 · 3 comments

Comments

@jkasarherou
Copy link
Contributor

jkasarherou commented Oct 2, 2017

event after rdir reassign, we encounter:

2017-10-02T13:52:22.515541+00:00 node01 OIO,OPENIO,oio-event-agent,0: warning  151249 7F30F93DD690 log WARNING event 176002 handling failure (release with delay): rdir update error: HTTPConnectionPool(host='127.0.0.1', port=6379): Max retries exceeded with url: /v1/rdir/push?vol=127.0.0.1%3A6278&create=1 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f30f678a850>: Failed to establish a new connection: [Errno 111] ECONNREFUSED',))

oio-proxy is still caching?

@jfsmig
Copy link
Contributor

jfsmig commented Oct 2, 2017

Similar to #1193

@jfsmig
Copy link
Contributor

jfsmig commented Nov 10, 2017

\cc @sebastienlapierre

@fvennetier
Copy link
Member

fvennetier commented Dec 5, 2017

oio-proxy is indeed caching service entries (unless proxy.cache.enabled=off). We could set resolver.cache.srv.ttl.default=15s to still benefit from the cache at service startup, but refresh the entry from time to time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants