UPDATE: The developers have a reproducible case now, and we are working on a fix. The data does actually persist to disk, but in an unaddressable way. It is recoverable using the `influx_inspect export` tool.
On Mon, Sep 26, 2016 at 8:25 PM, Sean Beckett <[email protected]> wrote: > There are two outstanding bugs with the ALTER RETENTION POLICY statement > that can lead to unexpected alterations, and in some cases, lost data. > > https://github.com/influxdata/influxdb/issues/5878 > When altering a retention policy, the system may continue issuing 204 > responses to writes, but the writes are not successfully persisted to disk. > > The corrective action is to alter the retention policy back to the precise > original syntax and settings. Writes should again persist. > > **If you have a reproducible case for this issue, please let us know. We > are still trying to recreate the issue on our test machines. > > https://github.com/influxdata/influxdb/issues/7150 > When altering a retention policy, the SHARD DURATION may be reset to "24h" > unless otherwise specified. This is not the intended behavior, as any > unspecified parameters should remain unchanged. > > The workaround is to always issue every parameter in the ALTER statement, > even those that don't change. > > > -- > Sean Beckett > Director of Support and Professional Services > InfluxDB > -- Sean Beckett Director of Support and Professional Services InfluxDB -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALGqCvM_XBEnjqKZg_0Kx%2B_tecrhiFM-JtbvOX65UAy-42Busw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
