[
https://issues.apache.org/jira/browse/HDDS-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906830#comment-16906830
]
Anu Engineer commented on HDDS-1871:
------------------------------------
I am getting the following error:
{noformat}
> kubectl get pod
NAME READY STATUS RESTARTS AGE
datanode-0 0/1 ImagePullBackOff 0 20m
om-0 0/1 ErrImagePull 0 20m
s3g-0 0/1 ImagePullBackOff 0 20m
scm-0 0/1 Init:ErrImagePull 0 20m
{noformat}
any idea what I am doing wrong ?
Here is my env.
* * minikube v1.3.1 on Darwin 10.14.5
* Kubernetes 1.15.2
* Docker 17.06.0-ce
> Remove anti-affinity rules from k8s minkube example
> ---------------------------------------------------
>
> Key: HDDS-1871
> URL: https://issues.apache.org/jira/browse/HDDS-1871
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: kubernetes
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Blocker
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> HDDS-1646 introduced real persistence for k8s example deployment files which
> means that we need anti-affinity scheduling rules: Even if we use statefulset
> instead of daemonset we would like to start one datanode per real nodes.
> With minikube we have only one node therefore the scheduling rule should be
> removed to enable at least 3 datanodes on the same physical nodes.
> How to test:
> {code}
> mvn clean install -DskipTests -f pom.ozone.xml
> cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/kubernetes/examples/minikube
> minikube start
> kubectl apply -f .
> kc get pod
> {code}
> You should see 3 datanode instances.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
