Well, indexes are just Bigtable rows, so replication lag does apply to them as well.
-- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Sep 20, 2011 at 7:42 AM, Mike Wesner <[email protected]> wrote: > And then I went and used the word replication... i meant index lag. > > On Sep 20, 9:40 am, Mike Wesner <[email protected]> wrote: > > I don't think Ikai read your post... > > > > Robert and I wanted to write a little HRD status site to track this > > and get real data, but we haven't done so yet. I have never seen the > > replication take more than about 1s. I think 1s will cover about four > > 9's, but that is just an educated guess. Until we (the users) > > actually measure this over time I don't think we can know for sure. > > > > -Mike > > > > On Sep 19, 7:16 pm, Jeff Schnitzer <[email protected]> wrote: > > > > > > > > > > > > > > > > > I know that an index update in the HRD will typically be visible > > > within a couple seconds. That's the average case. What is the > > > worst-case? > > > > > Assuming something in the datacenter goes wacky, how long might it > > > take for an index to update? Tens of seconds, minutes, hours, days? > > > > > Thanks, > > > Jeff > > -- > 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.
