Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define retention policy #447

Closed
rehevkor5 opened this issue May 16, 2016 · 3 comments
Closed

Define retention policy #447

rehevkor5 opened this issue May 16, 2016 · 3 comments

Comments

@rehevkor5
Copy link

The page mentioned below says:

Once those data have timestamps that are older than two hours, InfluxDB deletes those data.

I can assume the timestamp they're referring to is the value provided in the insert statement. However, it doesn't say what the timestamps are compared to in order to determine whether they're "older than two hours". Is it compared to the local server clock? A globally coordinated cluster clock? The most recent timestamp put into the database? table?

Or is it the insertion timestamp (from system clock) compared with the system clock?

It's important to know the details in case the timestamps being ingested are not be close to the value of the system clock.

URL for relevant page?

https://docs.influxdata.com/influxdb/v0.13/guides/downsampling_and_retention/

What products and version are you using?

InfluxDB 0.13

Where did you look before opening the issue?

Docs, GitHub issues, Google

@rkuchan
Copy link
Contributor

rkuchan commented May 16, 2016

@rehevkor5, InfluxDB compares the timestamps on the data to now() where now() is your local server's current timestamp.

I'll keep this issue open so that we clarify that behavior in the downsampling and retention guide. Thank you for pointing that out!

@rehevkor5
Copy link
Author

@rkuchan thanks for the quick answer!

@rkuchan
Copy link
Contributor

rkuchan commented Jun 9, 2016

Fixed by #499

@rkuchan rkuchan closed this as completed Jun 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants