Hi Ian, It has been confirmed that the error message is on a Measurement basis (not per shard).
If you are getting this error message its likely that the tags you are using are not the natural key for your data. Our current solution is to switch this setting off in the database and allocate more memory to the server. The long term solution is that I am working with the client to understand the data better and do some pre processing on the data that we are using as a Tag. Hope that helps Ivan On Friday, December 30, 2016 at 8:33:07 PM UTC, [email protected] wrote: > On Tuesday, November 29, 2016 at 3:47:22 AM UTC-5, Ivan Scattergood wrote: > > Hi, > > > > > > I have recently upgraded to version 1.1 of Influx and I noticed that the > max-values-per-tag setting is highlighting the fact that I am using a large > number of tags for certain measurements. > > > > > > However I notice this error appears to be on a per shard basis. Is my > understanding correct? > > > > > > The reason for my question is that the tag value changes over time and > so tags that were present a week ago might not be present in todays data. > > > > > > I'd also like to understand if this is a limit per measurement or per > database. Due to a restriction in Visualization tool I am using I re-use > the same tag name on separate measurements. > > > > > > Thanks as always for the help > > > > > > Ivan > > We're seeing the same thing .. did you find a fix? -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" 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/2a026f3d-2200-462a-90c4-d7a74dcc05ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
