Peter Bourgon
Peter Bourgon
Setting -cluster to 0.0.0.0 will always fail, so you can strike that. It's encouraging that each node sees an incrementing Join=n number as they boot up. But something is going...
I've recently cut [v0.2.1](https://github.com/oklog/oklog/releases/tag/v0.2.1) so you might prefer that instead.
Yep, so (long story short) when you set -cluster to that hostname, the memberlist library binds a TCP listener there, and later [introspects on the bound net.TCPConn.Addr](https://github.com/hashicorp/memberlist/blob/bbad45074a20fa539bc52e62d1e5f9f8cb467e7c/net_transport.go#L161) to deduce an...
I have no idea who is creating the OK Log Docker images. It's not me.
Nice! I want to capture a few more improvements for the next release. No ETA just yet. Thanks for working on the Helm chart, I'm excited to try it! I...
Haha! Wow. Yes, please.
It looks like the operative panic [is here](https://github.com/oklog/oklog/blob/7fa04d3c21f8fedb54940c069c02e450c7cc8eb3/pkg/store/read.go#L150): ```go // Per-segment state. writeSegment, err := dst.Create() if err != nil { return n, err } defer func() { // Don't...
Should be low/moderate, yes. What are the CPU and disk stats on those 3 store nodes?
To be honest I'm not sure this is even worth doing. I'd want to see pretty strong empirical evidence of benefit.
OK Log uses time component of ULID as primary key for all queries. Each record must retain some form of timestamp in its per-record prefix. I think a better angle...