Thanks Ikai.






On Thu, Jan 6, 2011 at 19:04, Ikai Lan (Google)
<[email protected]> wrote:
> Stephen,
> The times I gave earlier were estimates of how much replication delay is
> introduced in each replication scheme. The "eventually consistent" flag is
> for reads only and dictates whether or not you care to read from the
> "Master" datastore - reads will go to a slave if there are issues reaching
> the master.
>
> Robert, in future releases, we will allow developers to create aliases for
> their applications. Aliases are routing rules that will override the current
> routing. Unfortunately, these are not production ready, as we don't have any
> ACLs in place and there are edge cases. For developers that want to migrate
> to HR datastore right away and need an alias created (say, for HTTPS) and
> are willing to weather some weirdness around mail, XMPP and cron, I am happy
> to create the alias for them given that they can prove they own both
> applications (source and destination application). These developers can fill
> out a request for an application ID alias here:
> http://code.google.com/support/bin/request.py?contact_type=AppEngineBillingSupport
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> Blogger: http://googleappengine.blogspot.com
> Reddit: http://www.reddit.com/r/appengine
> Twitter: http://twitter.com/app_engine
>
>
> On Thu, Jan 6, 2011 at 3:56 PM, Stephen <[email protected]> wrote:
>>
>>
>> On Thursday, January 6, 2011 11:09:24 PM UTC, Ikai Lan (Google) wrote:
>>>
>>> - Typically, how long does it take for HR query data to become consistent
>>> (a ballpark figure)?
>>> 100ms is the estimate. However - we have seen cases where this can be
>>> higher. If you were to use the eventual consistency read option in the
>>> master-slave configuration, we've seen that the average replication lag is
>>> about 3 minutes with an upper bound of 10 minutes.
>>
>> What are the timings for the master/slave datastore with the
>> EVENTUALLY_CONSISTENT option?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to