-
Notifications
You must be signed in to change notification settings - Fork 84
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
Initial support for three data hall replication #1651
Initial support for three data hall replication #1651
Conversation
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr-kind on Linux CentOS 7
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to create a follow up issue to build e2e test cases for this configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I found a typo, but otherwise this looks good to me.
fe562f1
to
a8c689c
Compare
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
7508317
to
892c6a9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting for the e2e tests to pass. I will make a small annoncement about this in the forums, as I know a few people waiting for this feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
- Commit ID: 892c6a9
- Duration 2:49:03
- Result: ❌ FAILED
- Error:
Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
- Build Log terminal output (available for 30 days)
- Build Workspace zip file of the working directory (available for 30 days)
We've seen this failure a few times:
2023/10/12 16:52:33 reconciled name=fdb-cluster-ccrfs4x5, namespace=pr-464-x6hz2s62, generation:2
• [FAILED] [1121.240 seconds]
Operator Migrations when a migration is triggered and the namespace quota is limited [BeforeEach] should add the prefix to all instances [e2e, pr]
[BeforeEach] /codebuild/output/src2181315438/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_migrations/operator_migration_test.go:77
[It] /codebuild/output/src2181315438/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_migrations/operator_migration_test.go:104
[FAILED] Timed out after 600.000s.
Expected
<int64>: 2
to be zero-valued
In [BeforeEach] at: /codebuild/output/src2181315438/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_migrations/operator_migration_test.go:100 @ 10/12/23 16:52:33.427
------------------------------
I'm going to open an issue for it to fix it.
Same for:
• [FAILED] [1937.014 seconds]
Operator Upgrades upgrading a cluster without chaos [It] Upgrade from 7.1.37 to 7.3.15 [e2e, pr]
/codebuild/output/src2181315438/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/fixtures/upgrade_test_configuration.go:115
[FAILED] Unexpected error:
<*errors.errorString | 0xc00029fb40>:
timed out waiting for the condition
{
s: "timed out waiting for the condition",
}
occurred
In [It] at: /codebuild/output/src2181315438/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator_upgrades_variations/operator_upgrades_variations_test.go:119 @ 10/12/23 16:54:29.772
There were additional failures detected. To view them in detail run ginkgo -vv
------------------------------
Description
Fixes: #348
Type of change
Please select one of the options below.
Discussion
When running a FoundationDB cluster on public cloud providers it can be useful to use three data hall as redundancy more and spread Pods across multiple availability zones. So far the operator was not supporting this mode. Now the operator supports this mode with minimal code changes, the drawback is, that a user has to create 3
FoundationDBCluster
resources.Testing
I did some manual testing:
and
fdbcli
show the correct config:Documentation
Added to this PR.
Follow-up
We can improve the three data hall setup in the future to only require one single
FoundationDBCluster
resource, but that will require additional changes in the operator.As a follow up we could think about adding support for three_data_center as well. Based on my current understanding those modes are similar.