I am little bit skeptical about using Swift for this use case because of its eventual consistency issue. I am not sure Swift cluster is good to be used for this kind of problem. Please note that Swift cluster may give you old data at some point of time.
On Wed, Aug 27, 2014 at 4:12 PM, Steven Hardy <[email protected]> wrote: > On Wed, Aug 27, 2014 at 02:39:09PM +0530, Jyoti Ranjan wrote: > > I am curious to know about Swift role here. Can you elaborate little > bit > > please? > > I think Zane already covered it with "We just want people to stop polling > us, because it's killing our performance". > > Basically, if we provide the option for folks using heat at large scale to > poll Swift instead of the Heat API, we can work around some performance > issues a subset of our users have been experiencing due to the load of many > resources polling Heat (and hence the database) frequently. > > Steve > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
