[
https://issues.apache.org/jira/browse/HDDS-1871?focusedWorklogId=298953&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-298953
]
ASF GitHub Bot logged work on HDDS-1871:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Aug/19 19:50
Start Date: 21/Aug/19 19:50
Worklog Time Spent: 10m
Work Description: anuengineer commented on pull request #1180: HDDS-1871.
Remove anti-affinity rules from k8s minkube example
URL: https://github.com/apache/hadoop/pull/1180
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 298953)
Time Spent: 1.5h (was: 1h 20m)
> 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
> Fix For: 0.5.0
>
> Time Spent: 1.5h
> 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: [email protected]
For additional commands, e-mail: [email protected]
