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

Asked remote read write #4243

Closed
MoSunDay opened this Issue Jun 8, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@MoSunDay
Copy link

MoSunDay commented Jun 8, 2018

I wonder why some remote storage only provides a write operation, not a read, so how can the data written to the database be used?

From other if using remote read and wirte InfluxDB, every time a large number of queries memory is required for a double, because InfluxDB need memory cache results, and then give P8S results to vomit, P8S also need to save data memory, and then execute PromQL.

This is just my guess. Why not set a time period for the InfluxDB data to exist locally after it has been fetched? Future queries will only use P8S 'own memory overhead.

@krasi-georgiev

This comment has been minimized.

Copy link
Member

krasi-georgiev commented Jun 8, 2018

I think you will get a better answer for that in the devs Malling list

@MoSunDay

This comment has been minimized.

Copy link
Author

MoSunDay commented Jun 11, 2018

@MoSunDay MoSunDay closed this Jun 11, 2018

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.