hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (Jira)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1871) Remove anti-affinity rules from k8s minkube example
Date Wed, 21 Aug 2019 10:56:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912168#comment-16912168
] 

Elek, Marton commented on HDDS-1871:
------------------------------------

Thanks the review [~anu]

You should build a new image. By default the apache/ozone images are used which are not created
for SNAPSHOT builds.

I tested it again and it worked:


{code}
#To use docker daemon of the minikube vm:
eval $(minikube docker-env) 

#Don't need to push because of the previous line
mvn clean install -f pom.ozone.xml -Pdocker-build -DskipTests

cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/kubernetes/examples/minikube
kubectl apply -f .

kubectl get pod
{code}

{code}
NAME         READY   STATUS    RESTARTS   AGE
datanode-0   1/1     Running   0          10s
datanode-1   1/1     Running   0          8s
datanode-2   1/1     Running   0          5s
om-0         1/1     Running   0          10s
s3g-0        1/1     Running   0          10s
scm-0        1/1     Running   0          10s
{code}

I also fixed a few typo (prdatanodeetheus.io/path --> prometheus.io/path) and regenerated
all the resources files.


> 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: 1h 10m
>  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
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message