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.

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

What is the best Architecture of ClickHouse Cluster in production? #1272

Closed
jackpgao opened this Issue Sep 21, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@jackpgao
Copy link

commented Sep 21, 2017

  • In order to improve the query performance, I use 3 node as a cluster, as below, I have A/B/C node, all nodes have a local table which use MergeTree engine, and also have a Distributed engine table, as planed, the query is very fast(3 nodes query parallelly).

  • But my problem is, how to make sure the whole cluster high availability?

  • After checking the Doc, I use such architecture as blow:

  • The config file as below:
<remote_servers>
    <logs>
        <shard>
            <weight>1</weight>
            <internal_replication>false</internal_replication>
            <replica>
                <host>A</host>
                <port>9000</port>
            </replica>
            <replica>
                <host>A'</host>
                <port>9000</port>
            </replica>
        </shard>
        <shard>
            <weight>2</weight>
            <internal_replication>false</internal_replication>
            <replica>
                <host></host>
                <port>9000</port>
            </replica>
            <replica>
                <host>B'</host>
                <port>9000</port>
            </replica>
        </shard>
    </logs>
</remote_servers>
  • I use A', B' and C' as replica node, make sure I have at least one backup.

  • But the new problem is, how to solve the failover problem?

    • If the A' or B' or C' get down, how to rebuild a new replica with history data?
@jackpgao

This comment has been minimized.

Copy link
Author

commented Sep 23, 2017

Found that the replication engine can solve data loss problem.

But the failover solution is still not clear.

@jackpgao

This comment has been minimized.

Copy link
Author

commented Oct 10, 2017

As ClickHouse is multer-master replication, the best arch should be as below:

@jackpgao jackpgao closed this Oct 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.