Live data from Hacker News

ClickHouse as an alternative to Elasticsearch for log storage and analysis

pixeljets.com

11–20 of 140 posts

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#11
I don't have any production experience running Clickhouse, but I have used it on a side project for an OLAP workload. Compared to Postgres Clickhouse was a couple orders of magnitude faster (for the query pattern), and it was pretty easy to setup a single node configuration compared to lots of the "big data" stuff. Clickhouse is really a game changer.

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#12

Read that as "Clubhouse" on first glance ... ... and was quite intrigued :) PS: Tough crowd tonite ... It would appear local crowd does not take well to some tongue-in-cheek. Besides, it actually happened as described.-

Take my upvote, because the same happened to me.

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#13
post #7

Anyone know more lightweight alternative to (ELK) Elastic Stack? I found https://vector.dev but it seems to be only the "L" part.

Have you looked into Google Cloud Logging (Stackdriver)? It's the most affordable and decent-enough solution we've found. The only issue is querying can be slow on large volumes.

Have you tried creating a sink from stackdriver to bigquery?

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#14

I don't have any production experience running Clickhouse, but I have used it on a side project for an OLAP workload. Compared to Postgres Clickhouse was a couple orders of magnitude faster (for the query pattern), and it was pretty easy to setup a single node configuration compared to lots of the "big data" stuff. Clickhouse is really a game changer.

what happens when your data doesn't fit in a single node anymore?

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#16
My biggest problem with Elasticsearch is how easy it is to get data in there and think everything is just fine... until it falls flat on its face the moment you hit some random use case that, according to Murphy's law, will also be a very important one.

I wish Elasticsearch were maybe a little more opinionated in its defaults. In some ways Clickhouse feels like they filled the gap not having opinionated defaults created. My usage is from a few years back so maybe things have improved

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#17

I don't have any production experience running Clickhouse, but I have used it on a side project for an OLAP workload. Compared to Postgres Clickhouse was a couple orders of magnitude faster (for the query pattern), and it was pretty easy to setup a single node configuration compared to lots of the "big data" stuff. Clickhouse is really a game changer.

what happens when your data doesn't fit in a single node anymore?

[deleted]

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#18

Read that as "Clubhouse" on first glance ... ... and was quite intrigued :) PS: Tough crowd tonite ... It would appear local crowd does not take well to some tongue-in-cheek. Besides, it actually happened as described.-

Take my upvote, because the same happened to me.

Could not have been the only one :)

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#19

I don't have any production experience running Clickhouse, but I have used it on a side project for an OLAP workload. Compared to Postgres Clickhouse was a couple orders of magnitude faster (for the query pattern), and it was pretty easy to setup a single node configuration compared to lots of the "big data" stuff. Clickhouse is really a game changer.

what happens when your data doesn't fit in a single node anymore?

It scales to crazy numbers as you add nodes in 2018 CloudFlare was ingesting 11M rows per second into their CH cluster

Re: ClickHouse as an alternative to Elasticsearch for log storage and analysis

#20

My biggest problem with Elasticsearch is how easy it is to get data in there and think everything is just fine... until it falls flat on its face the moment you hit some random use case that, according to Murphy's law, will also be a very important one. I wish Elasticsearch were maybe a little more opinionated in its defaults. In some ways Clickhouse feels like they filled the gap not having opinionated defaults crea…

Would you care to elaborate on what happened in your case. My company is using ElasticSearch extensively, and it is mission critical for us. I fear something might happen one day
Post reply on HN