This message was deleted.
# supports
Slackbot
07/28/2022, 6:54 PMThis message was deleted.
a
Alexei Zenin
07/28/2022, 6:55 PMis it recommended to run more than 1 query service or any other of the above containers in PROD?
p
Prashant Shahi
07/28/2022, 8:57 PM@Alexei Zenin currently, Frontend and OtelCollector can be scaled.
It does not make sense to horizontally scale OtelCollector Metrics, as it is used for obtaining metrics via pull based mechanism.
Scaling ClickHouse is done using
layoutsa
Alexei Zenin
07/28/2022, 8:58 PMI see thanks, so alert manager and query service cannot
Alexei Zenin
07/28/2022, 8:59 PMIs there something stateful in the query-service?
p
Prashant Shahi
07/28/2022, 9:08 PMAlertmanager could be possible, but unsure since we haven't tested it from our end.
@Amol Umbark would be the right person to answer that.
Prashant Shahi
07/28/2022, 9:09 PMFor query-service, @Ankit Nayan would be the best person to answer that.
a
Ankit Nayan
07/29/2022, 4:46 AM
nothing specific in query-service except that we use a sqlite db for storing users and dashboards. When we add postgres, it will become horizontally scalable
Ankit Nayan
07/29/2022, 4:48 AM
but usually querying is not heavily used unless we have too many alerts running at fixed interval. Hence we separated ingestion and querying to handle both the loads separately
a
Alexei Zenin
07/29/2022, 2:23 PMYeah thats what I was thinking, the file DB would only allow 1 instance of query service. Thanks for the clarifications!
Alexei Zenin
07/29/2022, 2:24 PMMySQL would be better :)
p
Prashant Shahi
07/29/2022, 2:28 PM@Alexei Zenin we had been evaluating PostgreSQL as a replacement for SQLite..
But due to lack of bandwidth, it is not on top of our roadmap.
👍 3
5 Views