Geo Cluster docs should discuss memcache

Bug #1569512 reported by clayg on 2016-04-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)

Bug Description

Somewhere in here:

We should say that each regions proxies should use their own memcache pool to improve cache cohesiveness and response time.

When using something like tempauth there's a caveat trying to use a token generated in one region (and stored in it's local memcache pool) against another region (you'll have to re-auth for that region, and store the token per-region)

But with an authoritative auth server like Keystone or some LDAP integration each region would need only to validate the token once and cache the result in it's local memcache pool.

... but generally clients just stick to a single region when making requests - so it's sort of only win.

Changed in swift:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers