Replies: 1 comment 1 reply
-
|
We have three major component:
The In your architecture, maybe there are a few issues:
If you run My suggestion:
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah I was planning to run the compactor on the cloud instance. The expected volume of data is not big, it's just I prefer my queries to always be snappy. I will try to implement this following your suggestion later. |
Beta Was this translation helpful? Give feedback.
-
I have this idea. Since in OpenObserve model the server is stateless, I want to get advantage of it. I am planning to have 2 OpenObserve instances running with the same s3 storage:
I realize that I can't access the data not pushed yet to S3 but that is ok. I think I could also close UI access on the cloud instance completely after setup as it will be running as "backend" only.
Assuming my desktop machine internet connection is fast enough, will there be any issues with this setup ? As far as I understand these 2 instances don't even need to know about each other ? Or any synchronization is needed ? I guess I may need a cluster (and shared metadata) if I want to configure functions that work on ingestion while working on the local instance
Beta Was this translation helpful? Give feedback.
All reactions