Matthew Jaffee

This ticket was actually talking about the overhead in the format we use for the results of group by queries (I only know that because I was present when it...

Todd: put rows in SQLite BLOB fields... Seebs: Need to be careful of running into the 64 bit boundary with high cardinality fields and large shard widths.

I think the goal of this ticket is for Pilosa to be horizontally scalable in terms of the number of rows in a given field. Thinking about it a bit...

just saw this again running `go test -race` in `pilosa/server` - just merged master in the roaring-import branch `495af54c10c85facf96aacfe5fdb32d47ecdf033` ``` WARNING: DATA RACE Write at 0x00c000b54fc9 by goroutine 363: github.com/pilosa/pilosa/vendor/github.com/hashicorp/memberlist.(*Memberlist).aliveNode()...

Yeah, we definitely need to figure out why this happens... it's a bit strange. You might try increasing the suspicion-mult which will give the memberlist stuff a bit more time...

@dmibor would love to know if this issue has still be affecting you all and if the latest changes fix/improve it. It's been a fairly complex thing to track down,...

Yeah, no problem. Is it GROUP BY queries which seem to cause problems? I imagine this will be helped by reducing their memory footprint, but ultimately I think we'd like...

related to #1693

perhaps not identical, but related: https://github.com/pilosa/pilosa/issues/725

This import view work (unmerged) may end up being relevant to backup/restore strategy: https://github.com/pilosa/pilosa/pull/733