InfluxDB Clustering Design – Neither CP or AP

Re:InfluxDB Clustering Design – Neither CP or AP by AnIrishDuck on Wednesday June 03, 2015 @07:41PM (#9656601)

Looks interesting. This answers a lot of questions about primary data, but I'm interested to know how continuous queries [1] are handled.

If they're stored like any other data, the "inserts are far more likely than updates" assumption doesn't really make sense. For example, what if you have a continuous query grouped by year?

PS. "challenges" is mis-spelled in the last sentence.

1. http://influxdb.com/docs/v0.8/api/continuous_queries.html

[ Parent | on HN ]

Re:InfluxDB Clustering Design – Neither CP or AP by pauldix on Wednesday June 03, 2015 @10:09PM (#9657049)

Each of those continuous query data points would be an insert. I guess if you're recalculating it frequently, those new points would be updates, however, under non-failure conditions that won't be a problem.

If failure conditions occur, hinted handoff should take care of it, or the next CQ run that recomputes the result should make it correct after the failure condition is resolved.

Finally, those aren't contentious updates. You're not talking about multiple clients trying to make different updates to the exact same point, which is really what I mean when I talk about not optimizing for updates.

[ Parent | on HN ]