Skip to content

Add TypeDB Cluster support and failover #765

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

Draft
farost wants to merge 1 commit into
base: cluster-support-feature-branch
Choose a base branch
from
Draft

Add TypeDB Cluster support and failover #765

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 7 additions & 8 deletions .circleci/config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -925,14 +925,13 @@ workflows:
- deploy-snapshot-any
# - deploy-snapshot-dotnet-any

# TODO: Windows typedb artifact is not ready
# - test-snapshot-windows-x86_64:
# filters:
# branches:
# only: [master]
# requires:
# - deploy-snapshot-windows-x86_64
# - deploy-snapshot-any
- test-snapshot-windows-x86_64:
filters:
branches:
only: [master]
requires:
- deploy-snapshot-windows-x86_64
- deploy-snapshot-any
# - deploy-snapshot-dotnet-any

# TODO: npm is not ready
Expand Down
110 changes: 55 additions & 55 deletions .factory/automation.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,8 +87,8 @@ build:

tool/docs/update_readme.sh
git add .
git diff --exit-code || {
echo "Failed to verify README files: plese update it manually and verify the changes"
git diff --exit-code || {
echo "Failed to verify README files: please update it manually and verify the changes"
exit 1
}

Expand All @@ -109,7 +109,7 @@ build:
if [[ -n "$COMMUNITY_FAILED" ]]; then exit 1; fi

# TODO: Use cluster server artifact with 3 nodes for the same common tests when available
# tool/test/start-cluster-servers.sh 3 &&
# source tool/test/start-cluster-servers.sh 3 &&
# bazel test //rust/tests/integration:all --test_output=streamed --test_arg=--nocapture &&
# export CLUSTER_FAILED= || export CLUSTER_FAILED=1
# tool/test/stop-cluster-servers.sh
Expand All @@ -129,22 +129,22 @@ build:
tool/test/stop-community-server.sh
exit $TEST_SUCCESS

# TODO: Use cluster server artifact with 3 nodes when available (it would do the same thing as community now)
# test-rust-behaviour-cluster:
# image: typedb-ubuntu-20.04 # Ubuntu 20.04 has GLIBC version 2.31 (2020) which we should verify to compile against
# dependencies:
# - build
# command: |
# export ARTIFACT_USERNAME=$REPO_TYPEDB_USERNAME
# export ARTIFACT_PASSWORD=$REPO_TYPEDB_PASSWORD
# bazel run @typedb_dependencies//tool/bazelinstall:remote_cache_setup.sh
# bazel run @typedb_dependencies//distribution/artifact:create-netrc
#
# tool/test/start-cluster-servers.sh 3 &&
# bazel test //rust/tests/behaviour/... --//rust/tests/behaviour/config:mode=cluster --test_output=streamed --jobs=1 &&
# export TEST_SUCCESS=0 || export TEST_SUCCESS=1
# tool/test/stop-cluster-servers.sh
# exit $TEST_SUCCESS
# TODO: Use cluster server artifact with 3 nodes when available (it currently uses 1)
test-rust-behaviour-cluster:
image: typedb-ubuntu-20.04 # Ubuntu 20.04 has GLIBC version 2.31 (2020) which we should verify to compile against
dependencies:
- build
command: |
export ARTIFACT_USERNAME=$REPO_TYPEDB_USERNAME
export ARTIFACT_PASSWORD=$REPO_TYPEDB_PASSWORD
bazel run @typedb_dependencies//tool/bazelinstall:remote_cache_setup.sh
bazel run @typedb_dependencies//distribution/artifact:create-netrc

source tool/test/start-cluster-servers.sh 1 &&
bazel test //rust/tests/behaviour/... --test_env=ROOT_CA=$ROOT_CA --//rust/tests/behaviour/config:mode=cluster --test_output=streamed --jobs=1 &&
export TEST_SUCCESS=0 || export TEST_SUCCESS=1
tool/test/stop-cluster-servers.sh
exit $TEST_SUCCESS

test-c-integration:
image: typedb-ubuntu-20.04 # Ubuntu 20.04 has GLIBC version 2.31 (2020) which we should verify to compile against
Expand Down Expand Up @@ -176,7 +176,7 @@ build:
if [[ -n "$COMMUNITY_FAILED" ]]; then exit 1; fi

# TODO: Use cluster server artifact with 3 nodes for the same common tests when available
# tool/test/start-cluster-servers.sh 3 &&
# source tool/test/start-cluster-servers.sh 3 &&
# bazel test //java/test/integration:all --test_output=streamed --jobs=1 &&
# export CLUSTER_FAILED= || export CLUSTER_FAILED=1
# tool/test/stop-cluster-servers.sh
Expand All @@ -196,22 +196,22 @@ build:
tool/test/stop-community-server.sh
exit $TEST_SUCCESS

# TODO: Use cluster server artifact with 3 nodes when available (it would do the same thing as community now)
# test-java-behaviour-cluster:
# image: typedb-ubuntu-22.04
# dependencies:
# - build
# command: |
# export ARTIFACT_USERNAME=$REPO_TYPEDB_USERNAME
# export ARTIFACT_PASSWORD=$REPO_TYPEDB_PASSWORD
# bazel run @typedb_dependencies//tool/bazelinstall:remote_cache_setup.sh
# bazel run @typedb_dependencies//distribution/artifact:create-netrc
#
# tool/test/start-cluster-servers.sh 3 &&
# .factory/test-cluster.sh //java/test/behaviour/... --test_output=streamed --jobs=1 &&
# export TEST_SUCCESS=0 || export TEST_SUCCESS=1
# tool/test/stop-cluster-servers.sh
# exit $TEST_SUCCESS
# TODO: Use cluster server artifact with 3 nodes when available (it currently uses 1)
test-java-behaviour-cluster:
image: typedb-ubuntu-22.04
dependencies:
- build
command: |
export ARTIFACT_USERNAME=$REPO_TYPEDB_USERNAME
export ARTIFACT_PASSWORD=$REPO_TYPEDB_PASSWORD
bazel run @typedb_dependencies//tool/bazelinstall:remote_cache_setup.sh
bazel run @typedb_dependencies//distribution/artifact:create-netrc
source tool/test/start-cluster-servers.sh 1 &&
.factory/test-cluster.sh //java/test/behaviour/... --test_env=ROOT_CA=$ROOT_CA --test_output=streamed --jobs=1 &&
export TEST_SUCCESS=0 || export TEST_SUCCESS=1
tool/test/stop-cluster-servers.sh
exit $TEST_SUCCESS

test-python-integration:
image: typedb-ubuntu-22.04
Expand All @@ -230,7 +230,7 @@ build:
if [[ -n "$COMMUNITY_FAILED" ]]; then exit 1; fi

# TODO: Use cluster server artifact with 3 nodes when available
# tool/test/start-cluster-servers.sh 3 &&
# source tool/test/start-cluster-servers.sh 3 &&
# bazel test //python/tests/integration:all --test_output=streamed --jobs=1 &&
# export CLUSTER_FAILED= || export CLUSTER_FAILED=1
# tool/test/stop-cluster-servers.sh
Expand All @@ -252,24 +252,24 @@ build:
tool/test/stop-community-server.sh
exit $TEST_SUCCESS

# TODO: Use cluster server artifact with 3 nodes when available (it would do the same thing as community now)
# test-python-behaviour-cluster:
# image: typedb-ubuntu-22.04
# dependencies:
# - build
# type: foreground
# command: |
# export PATH="$HOME/.local/bin:$PATH"
# export ARTIFACT_USERNAME=$REPO_TYPEDB_USERNAME
# export ARTIFACT_PASSWORD=$REPO_TYPEDB_PASSWORD
# bazel run @typedb_dependencies//tool/bazelinstall:remote_cache_setup.sh
# bazel run @typedb_dependencies//distribution/artifact:create-netrc
#
# tool/test/start-cluster-servers.sh 3 &&
# .factory/test-cluster.sh //python/tests/behaviour/... --test_output=streamed --jobs=1 &&
# export TEST_SUCCESS=0 || export TEST_SUCCESS=1
# tool/test/stop-cluster-servers.sh
# exit $TEST_SUCCESS
# TODO: Use cluster server artifact with 3 nodes when available (it currently uses 1)
test-python-behaviour-cluster:
image: typedb-ubuntu-22.04
dependencies:
- build
type: foreground
command: |
export PATH="$HOME/.local/bin:$PATH"
export ARTIFACT_USERNAME=$REPO_TYPEDB_USERNAME
export ARTIFACT_PASSWORD=$REPO_TYPEDB_PASSWORD
bazel run @typedb_dependencies//tool/bazelinstall:remote_cache_setup.sh
bazel run @typedb_dependencies//distribution/artifact:create-netrc
source tool/test/start-cluster-servers.sh 1 &&
.factory/test-cluster.sh //python/tests/behaviour/... --test_env=ROOT_CA=$ROOT_CA --test_output=streamed --jobs=1 &&
export TEST_SUCCESS=0 || export TEST_SUCCESS=1
tool/test/stop-cluster-servers.sh
exit $TEST_SUCCESS


test-http-ts-behaviour-community:
Expand Down
Loading