citusdata / citusdata/citus

Cluster block query when one node down.

Open
#6,174 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
12.8k
Forks
794
Avg merge
2d 14h
Merged PRs (30d)
31

Description

I follow the instruction to create a citus cluster with 5 worker and set the replication factor to 3. (With docker-compose -p citus up and scaled the worker to 5)
Then created a distributed test_table as described in the official online document. Inserted 100k data to the database.
I verifyed the shards are distributed by using SELECT * FROM pg_dist_shard_placement, and successfully ran the select * from master server.

Then I was trying to test the high availability, so I shutdown one worker1 and tried the same query select * from test_table.

The expected result will be 100000 returned immediately, since there's a high availability natively built in.
The actual result is, the query will be blocked all the way to the expiration. Unless I restart the "failed" node during the blocking time.

I was expecting the cluster to automatically redirect the query to other available worker nodes with the same shards stored in worker 1.Is there anything else I have to do beyond using the "official docker images and instruction"

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.