On Thu, Aug 18, 2016 at 3:07 PM, Emiliano Heyns < [email protected]> wrote:
> On Thursday, August 18, 2016 at 10:43:26 PM UTC+2, Sean Beckett wrote: >> >> You can actually install 1.0-nightlies while InfluxDB 0.13 is still >> running, then update the config files >> > > But looking at the changelog, and given that I don't expect I'll be > hitting the default million max-series-per-database in the next two > decades, I can probably just leave the existing config, right? I currently > have 3 series, each with one tag with cardinality 3, with approx 70 fields > on the series. > Practically, yes, you can ignore the config changes for this upgrade. Eventually it is important to purge old config entries and make sure new ones are well-set, but the 1.0 final release would be a good time for that focus. > > >> and bounce the process to move to the new code. TSM can export against a >> running instance, but it's cleaner to make a working copy of the TSM file >> elsewhere to avoid multiple read/write locks on the file. >> > > Cleaner in what sense? Could the DB get corrupted (not good) or would > readers/writers/exporters throw errors if they meet each other > (acceptable). There are known windows where it's exceedingly unlikely that > readers/writers will be active; if they are and all that happens is that > they get an error, that's fine. > Cleaner in the sense that there's not contention between influxd and influx_inspect for the same file. There's no real chance of corruption, but there could be a deadlock issue between the two independent processes each seeking a read lock with influxd also looking for write locks. > > Thanks, > Emile > >> -- > 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/f93bed4a-1adb-4b74-88b8-3c3f504f0621%40googlegroups.com > <https://groups.google.com/d/msgid/influxdb/f93bed4a-1adb-4b74-88b8-3c3f504f0621%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CALGqCvNbN9-eApc7t2b%3Dcz8mQOpabbm25MJNs436%2B-uufGnR5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
