Hi,
(http://permalink.gmane.org/gmane.comp.file-systems.ceph.devel/12316)
> Hopefully not Varnish-specific; something like the Last-Modified header
> would be good.
>
> Also there are tricks you can do with queries; see for instance
> http://forum.nginx.org/read.php?2,1047,1052
It seems like a good discussion to have, since more people are looking
at this.
Yehuda started a thread in May last year about the future directions of
the RGW: http://www.spinics.net/lists/ceph-devel/msg06257.html
To improve performance I still think using a proxy like Varnish or Nginx
can help a lot.
Now, when running just one Varnish instance which does loadbalancing
over multiple RGW instances is not a real problem. When it sees a PUT
operation it can "purge" (called banning in Varnish) the object from
it's cache.
When looking at the scenario where you have multiple caches you run into
the cache-consistency problem. If an object is modified the caches are
not notified and will continue to serve an outdated object.
Looking at the Last-Modified header is not an option since the cache
will not contact RGW when serving out of it's cache.
To handle this there has to be some kind of "hook" inside RGW that can
notify Varnish (or some other cache) when an object changes.
Is this something that's on the roadmap? Thoughts?
Wido
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
