Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEO updates, added nofollow to clickhouse.tech links #130

Merged
merged 2 commits into from
Feb 19, 2025
Merged

SEO updates, added nofollow to clickhouse.tech links #130

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
886198c
SEO updates, added nofollow to clickhouse.tech links
DougTidwell Feb 19, 2025
4d3cf6a
Merge branch 'main' into sphoorti
DougTidwell Feb 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...b-setup-and-maintenance/altinity-kb-data-migration/distributed-table-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ keywords:
- clickhouse distributed
---

In order to shift INSERTS to a standby cluster (for example increase zone availability or disaster recovery) some ClickHouse® features can be used.
In order to shift INSERTS to a standby cluster (for example increase zone availability or [disaster recovery](https://docs.altinity.com/operationsguide/availability-and-recovery/recovery-architecture/)) some ClickHouse® features can be used.

Basically we need to create a distributed table, a MV, rewrite the `remote_servers.xml` config file and tune some parameters.

Expand Down Expand Up @@ -118,7 +118,7 @@ All the hostnames/FQDN from each replica/node must be accessible from both clust

### Configuration settings

Depending on your use case you can set the the distributed INSERTs to sync or async mode. This example is for async mode:
Depending on your use case you can set the the distributed INSERTs to sync or [async mode](/altinity-kb-queries-and-syntax/async-inserts/). This example is for async mode:
Put this config settings on the default profile. Check for more info about the possible modes:

https://clickhouse.com/docs/en/operations/settings/settings#insert_distributed_sync
Expand Down
2 changes: 1 addition & 1 deletion layouts/_default/_markup/render-link.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
<a href="{{ .Destination | safeURL }}"{{ with .Title}} title="{{ . }}"{{ end }}{{ if strings.HasPrefix .Destination "http" }} target="_blank"{{ end }}{{ if strings.Contains .Destination "clickhouse.com" }} rel="nofollow" {{ end }}>{{ .Text }}</a>
<a href="{{ .Destination | safeURL }}"{{ with .Title}} title="{{ . }}"{{ end }}{{ if strings.HasPrefix .Destination "http" }} target="_blank"{{ end }}{{ if strings.Contains .Destination "clickhouse.com" }} rel="nofollow" {{ end }}{{ if strings.Contains .Destination "clickhouse.tech" }} rel="nofollow" {{ end }}>{{ .Text }}</a>