Bernd Zeimetz

@ilyakimavets just put an haproxy instance in front of carbon clickhouse...

But instead of changing the table schema, is there an issue in using toYYYYMMDD() for partitioning? Optimizing > 1.5TB partitions down to ~100G just needs an useless amount of empty...

> It's something I can answer > > > But instead of changing the table schema, is there an issue in using toYYYYMMDD() for partitioning? > > It depends more...

The default keepalive-timeout in CH is 3 seconds, while the default keepalive time used by net.Dialer is 15 seconds. That won't work.

Using ``` diff --git a/proxy.go b/proxy.go index 11684b6..356cd2c 100644 --- a/proxy.go +++ b/proxy.go @@ -3,6 +3,7 @@ package main import ( "context" "fmt" + "net" "net/http" "net/http/httputil" "net/url" @@ -43,6...

Seems to make things better, but doesn't fix them unfortunately.

```Jul 07 11:48:00 mon01 chproxy[40652]: ERROR: 2021/07/07 09:48:00 proxy.go:48: http: proxy error: net/http: HTTP/1.x transport connection broken: write tcp 127.0.0.1:58570->127.0.0.1:8123: write: broken pipe```

any news on this issue? ipv6 support would be really great to have!

As you can connect a normal prometheus as remote reader - I'm wondering if its needed to have a prometheus integrated. Providing the remote storage endpoint and running a prometheus...

Ah sorry, I've missed that / is being routed into prometheus. I thought that the remote read/write interface was different code.