-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Cassandra Example: #235
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
Comments
Getting the same error. Just followed the steps in https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ Here's the startup log:
|
I just pointed this yaml to the official Cassandra image and it came up fine. |
@mikep-locol-media : Thank you for the info, we are using official Cassandra image but we got below error could you please let us know what SEED Configuration you have used |
Looks like it could not find cassandra-0.cassandra.default.svc.cluster.local. Is this right? Are you running under the default namespace? Unfortunately I am in the hospital today otherwise I can put up my yaml files. |
yes , i am using default namespace ubuntu@xyz:~/cluster-deployment/kubernetes$ kubectl get pods --all-namespaces tomorrow is fine , get well |
Ah. Is your pod cassandra-1? The url is looking for cassandra-0 |
Try changing the seed url to -1 |
i changed pod to Cassandra-0, still no luck . i have used exact same yaml's and both v14 & apache cass 3.11 no luck when i try to bring up it gets stuck at pending state ubuntu@ip-xyz:~/cluster-deployment/kubernetes$ kubectl get pods I0613 21:20:13.973078 11972 round_trippers.go:386] curl -k -v -XGET -H "Accept: application/json, /" -H "User-Agent: kubectl/v1.10.3 (linux/amd64) kubernetes/2bba012" https://A89CFD1F959FBD470AF412E2D2563BCE.yl4.us-west-2.eks.amazonaws.com/api/v1/namespaces/default/pods/cassandra-0 |
if possible could you provide aws storage class example |
@mikep-locol-media : we were able to resolve the ebs volume issue but we still facing same error as above ("seed provider error ") : could you send your yaml you have used for Apache Cassandra Image . INFO 19:45:59 DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap |
Hi.. these are my yaml files. Notes:
|
Yes, I thought of trying aledbf/cassandra:v15. Just thought that switching over to the official cassandra was a better long term switch. |
@mikep-locol-media : i was able to bring official cassandra , but during bootsrap few nodes restarted, but they joined the ring eventually INFO [main] 2018-06-14 23:41:06,177 StorageService.java:1449 - JOINING: waiting for schema information to complete |
I find a lot of k8s stuff takes a bit of time to get themselves sorted out starting. Have not dug into it. |
@mikep-locol-media : could you please share github project link for your controller file |
Sorry, which controller file? I uploaded my cassandra yaml files in my previous post. I do not have it in a github repo. I have k8s clusters on GKE and also on Docker for Mac, if that is relevent. |
@mikep-locol-media : one last question any idea how below seed provider class is being referenced in your controller cassandra-statefulset.yaml .is this something built into . image: cassandra - name: CASSANDRA_SEED_PROVIDER https://hub.docker.com/_/cassandra/ appreciate your help |
@mikep-locol-media : just to add above i would like to know if below particular jar file is embedded in Cassandra Image |
I ran into this same issue. I solved this by creating my own image from gcr.io/google-samples/cassandra:v14 with 1 change: I also had to give the service account the pod was using read access to endpoints in the namespace. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@Bfoster-melrok it seems like you shouldn't have to do what you suggested in #235 (comment) but that seems like an ok workaround. When I was trying to investigate what was going on yesterday, it doesnt seem like the exported |
I am encountering this problem when loading v14 of the example. I don' know if this relates to #89
Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered during startup: io.k8s.cassandra.KubernetesSeedProvider
Fatal configuration error; unable to start server. See log for stacktrace.
org.apache.cassandra.exceptions.ConfigurationException: io.k8s.cassandra.KubernetesSeedProvider
Attached is the startup log.
logs-from-cassandra-in-cassandra-0.txt
The text was updated successfully, but these errors were encountered: