-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Cassandra Cluster Example Custom Seed Cores on First Node #5737
Labels
area/example
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
Comments
Thanks for the detailed report! Any chance you'd be willing to open a PR for this? |
mbforbes
added
priority/backlog
Higher priority than priority/awaiting-more-evidence.
area/example
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
labels
Mar 21, 2015
I would be willing to open a PR. |
mikeln
added a commit
to mikeln/kubernetes
that referenced
this issue
Mar 21, 2015
mikeln
added a commit
to mikeln/kubernetes
that referenced
this issue
Mar 21, 2015
mikeln
added a commit
to mikeln/kubernetes
that referenced
this issue
Mar 22, 2015
mikeln
added a commit
to mikeln/kubernetes
that referenced
this issue
Mar 23, 2015
This was referenced Mar 23, 2015
Update the cassandra example to pick up recent changes. #5857 |
Fixed by #5857. |
jayunit100
pushed a commit
to jayunit100/kubernetes
that referenced
this issue
Mar 26, 2015
akram
pushed a commit
to akram/kubernetes
that referenced
this issue
Apr 7, 2015
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/example
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
examples/cassandra startup of cassandra pod with the custom Java seed provider code cores on the first pod:
The io.k8s.cassandra.KubernetesSeedProvider.getSeeds pulls the seed addresses from kubernetes. Here is what this container was seeing:
Analysis showed the following:
Prototyped a fix by adding:
Suggest incorporating this modification
The text was updated successfully, but these errors were encountered: