Pgalbraith backup doc container doc fix #1081
Conversation
…ed files to avoid too large numbers in logs Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
Altinity#1060, fix Altinity#313 Signed-off-by: Slach <[email protected]>
…Altinity#505 (comment) Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
fix Altinity#877 (comment)), fix Altinity#505 (comment) Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
…ration and significant decrease memory usage during upload and download, fix [854](Altinity#854) Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
…ltinity#1075 Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
…nload` command, fix Altinity#1042 Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
…nly` options to `upload` and `download` command, fix Altinity#1042 Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
…ands, with table pattern to allow make backup without projection fix Altinity#861 Signed-off-by: Slach <[email protected]>
…mmands, with table pattern to allow make backup without projection, restore supported only in `clickhouse-server` 24.3+, fix Altinity#861 Signed-off-by: Slach <[email protected]>
Replace `backups` dir name with `backup` in command example.
…doesn't work in k8s clusters running arm64 arch
|
looks weird, how did you make 24 commits instead of just last two |
| @@ -319,7 +321,7 @@ spec: | |||
| restartPolicy: Never | |||
| containers: | |||
| - name: run-backup-cron | |||
| image: clickhouse/clickhouse-client:latest | |||
| image: clickhouse/clickhouse-server:latest | |||
There was a problem hiding this comment.
let's add comment here about clickhouse-client doesn't support anymore, to avoid comments about "ah why you run second clickhouse-server?"
actually old clickhouse-clients should connect to latest clickhouse-server, protocol compatible, which kind of issue did you look here?
There was a problem hiding this comment.
my issue was that the container in the cron was failing with an odd 'bash exec' issue when I tried running the container in kubernetes with a simple bash while loop to test in aws-dev-eu (which the nodes are arm64). Some searching and a test on my own laptop (which is arm64) gave me the same error, then I realized that the clickhouse-client container didn't run on arm64. Both Anselmo and Josh pointed out what I had suspected and suggested clickhouse-server
There was a problem hiding this comment.
ok. got it
https://hub.docker.com/r/clickhouse/clickhouse-client/tags
doesn't support arm64, lets add comment here
Pull Request Test Coverage Report for Build 13044819465Details
💛 - Coveralls |
yes, I didn't realize this. I did a rebase of my fork, I'll redo this. |
I needed to use
clickhouse-servercontainer image instead ofclickhouse-clientimage, which the latter didn't work in aws-dev-eu because of it being arm64. I also elaborated how the process works a bit more.