-
Notifications
You must be signed in to change notification settings - Fork 39
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
M3DB Operator Timing Out Waiting for Instances #166
Comments
It looks like this might be related to the workaround for issue #137. I commented out the lines in my cluster create script that patch the stateful sets and now m3db coordinator is able to find the instances:
The logs from the nodes also support that things are being bootstrapped properly:
Unfortunately, it doesn't appear to be working fully yet. I still get an error trying to list out placements:
And while I can create a database:
I'm unable to see it listed in via the API (tried to create default2 but only default is listed):
|
Thanks for opening an issue for the M3DB Operator! We'd love to help you, but we need the following information included
with any issue:
master
, please include the gitSHA logged when the operator first starts.
2.3.2
kubectl version
.Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Create a cluster using a
M3DBCluster
spec. The M3DB operator created 3 pods:I have verified that there is a placement group defined in Etcd that matches these nodes (excluding the output from that command as I cannot get GitHub to format it correctly).
I am using
.podIdentifyConfig.sources.NodeName
to set the node identity, as I'm trying to configure this oni3en
instances providing fast, local SSD storage at a reasonable price point. I'm using the local storage provisioner to mount a file system under thedataDirVolumeClaimTemplate
part of the spec.I expected the cluster to come up with a valid placement group.
Each of the nodes are coming up but the m3db operator is complaining that it's timing out waiting for the instances:
However, if I try to get the placement using the Coordinator, I get:
Here are the logs from one of the nodes:
The text was updated successfully, but these errors were encountered: