Yes, after version and agent ensuring to pick correct data will not cause
Swift issue.
On Thu, Aug 28, 2014 at 2:59 AM, Steve Baker sba...@redhat.com wrote:
On 28/08/14 03:41, Zane Bitter wrote:
On 27/08/14 11:04, Steven Hardy wrote:
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan
I am curious to know about Swift role here. Can you elaborate little bit
please?
On Wed, Aug 27, 2014 at 4:14 AM, Steve Baker sba...@redhat.com wrote:
On 23/08/14 07:39, Zane Bitter wrote:
We held the inaugural Heat mid-cycle meetup in Raleigh, North Carolina
this week. There were a dozen
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
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
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan wrote:
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
On 27/08/14 11:04, Steven Hardy wrote:
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan wrote:
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.
Swift does have some guarantees around read-after-write consistency, but
for Heat I think the best bet would be the X-Newest[1] header which has
been in swift for a very, very long time. The downside here is that
(IIUC) it queries all storage nodes for that object. It does not provide
a hard
Excerpts from Zane Bitter's message of 2014-08-27 08:41:29 -0700:
On 27/08/14 11:04, Steven Hardy wrote:
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan wrote:
I am little bit skeptical about using Swift for this use case because
of
its eventual consistency issue. I am not
On Wed, Aug 27, 2014 at 11:41:29AM -0400, Zane Bitter wrote:
On 27/08/14 11:04, Steven Hardy wrote:
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan wrote:
I am little bit skeptical about using Swift for this use case because of
its eventual consistency issue. I am not sure Swift
On Wed, Aug 27, 2014 at 09:40:31AM -0700, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-08-27 08:41:29 -0700:
On 27/08/14 11:04, Steven Hardy wrote:
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan wrote:
I am little bit skeptical about using Swift for this use
Excerpts from Steven Hardy's message of 2014-08-27 10:08:36 -0700:
On Wed, Aug 27, 2014 at 09:40:31AM -0700, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-08-27 08:41:29 -0700:
On 27/08/14 11:04, Steven Hardy wrote:
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan
On 28/08/14 03:41, Zane Bitter wrote:
On 27/08/14 11:04, Steven Hardy wrote:
On Wed, Aug 27, 2014 at 07:54:41PM +0530, Jyoti Ranjan wrote:
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
On Fri, Aug 22, 2014 at 03:39:24PM -0400, Zane Bitter wrote:
We held the inaugural Heat mid-cycle meetup in Raleigh, North Carolina this
week. There were a dozen folks in attendance, and I think everyone agreed
that it was a very successful event. Notes from the meetup are on the
Etherpad
On 23/08/14 07:39, Zane Bitter wrote:
We held the inaugural Heat mid-cycle meetup in Raleigh, North Carolina
this week. There were a dozen folks in attendance, and I think
everyone agreed that it was a very successful event. Notes from the
meetup are on the Etherpad here:
Zane Bitter wrote:
[...]
Here are a few of the conclusions:
* Everyone wishes the Design Summit worked like this.
The meetup seemed a lot more productive than the design summit ever is.
It's really nice to be in a room small enough that you can talk normally
and hear everyone, instead of
On 25/08/14 05:21, Thierry Carrez wrote:
Zane Bitter wrote:
[...]
Here are a few of the conclusions:
* Everyone wishes the Design Summit worked like this.
The meetup seemed a lot more productive than the design summit ever is.
It's really nice to be in a room small enough that you can talk
16 matches
Mail list logo
