Member since
04-20-2017
14
Posts
1
Kudos Received
0
Solutions
07-07-2017
07:52 AM
Thanks for the answers. The described steps solve the DNS change for Manager indeed. For director, I will use a pre-baked Manager AMI as suggested.
... View more
07-04-2017
07:43 AM
Hi, I created a deployment and a cluster using Director. After the EC2 instances were running and cluster was all set up, I changed the hostname of the instances. Now, I want to update the hostnames in the Manager, (and also the Manager's hostname in Director) because they point to the old ones (ip-xxxxx.eu-west-1.compute.internal) Is there a way to do that? I found https://www.cloudera.com/documentation/enterprise/5-7-x/topics/cm_ag_change_hostnames.html, but I hope there is an easier solution to that. Is it possible to tell Director/Manager to use a specific hostnames when creating the cluster? Or do I need to run a script and change the hostnames before Director starts to install the services on the nodes?
... View more
Labels:
- Labels:
-
Cloudera Manager
06-29-2017
09:01 AM
Hi Bill, thanks for the tips, setting "enable_api_debug: true" helped identifying the issue. It seems that the Oozie service is a requirement for Hue - After I included Oozie, the creation ran successfully.
... View more
06-29-2017
03:20 AM
I'm using Director's Rest API to start a cluster on an existing deployment. It runs fine until the firstRun call, at this step I see this error in the director logs: [2017-06-29 09:53:38.054 +0000] INFO [p-859d12b97f1e-DefaultBootstrapClusterJob] POST /api/v8/environments/dwh/deployments/manager_live/clusters com.cloudera.launchpad.bootstrap.cluster.firstrun.InvokeFirstRunClusterCommandV7 - c.c.l.pipeline.util.PipelineRunner: >> InvokeFirstRunClusterCommandV7/3 [Environment{name='dwh', provider=InstanceProviderConfig{type='aws'}, credentials=SshCred ...
[2017-06-29 09:53:38.094 +0000] INFO [p-859d12b97f1e-DefaultBootstrapClusterJob] POST /api/v8/environments/dwh/deployments/manager_live/clusters com.cloudera.launchpad.bootstrap.cluster.firstrun.InvokeFirstRunClusterCommandV7 - c.c.launchpad.pipeline.AbstractJob: Calling firstRun on cluster dwh_live
[2017-06-29 09:53:38.142 +0000] ERROR [p-859d12b97f1e-DefaultBootstrapClusterJob] POST /api/v8/environments/dwh/deployments/manager_live/clusters com.cloudera.launchpad.bootstrap.cluster.firstrun.InvokeFirstRunClusterCommandV7 - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed
com.cloudera.api.ext.ClouderaManagerException: API call to Cloudera Manager failed. Method=ClustersResourceV7.firstRun. Response Status Code: 400. - Cause: javax.ws.rs.BadRequestException HTTP 400 Bad Request
at com.cloudera.api.ext.ClouderaManagerClientProxy.invoke(ClouderaManagerClientProxy.java:137)
at com.sun.proxy.$Proxy257.firstRun(Unknown Source)
... I was looking for logs on the Manager, but could not find anything useful. Which log file should give me more insights? The cluster would be fairly simple, with a master node, one worker and a gateway. The services use an external RDS database, the same that is used by the Manager. What can be the issue here?
... View more
Labels:
- Labels:
-
Cloudera Manager
06-26-2017
07:13 AM
I'd like to add a deployment to my existing environment using the Rest API, with an existing external Database Server, and using existing instance templates. I found in the API docs, that this is the way to add a deployment, but this creates a new template, however I want to use my existing ones. Is it possible to reference them somehow? {
"name": "",
"managerVirtualInstance": {
"id": "",
"template": {
"name": "",
"type": "",
"image": "",
"config": "object",
"tags": "object",
"normalizeInstance": false,
"sshUsername": "",
"bootstrapScripts": [
""
]
}
},
"externalDatabaseTemplates": [
{
"key": {
"name": "",
"databaseServerName": "",
"databaseNamePrefix": "",
"usernamePrefix": ""
}
}
],
"externalDatabases": [
{
"key": {
"type": "",
"host": "",
"port": 0,
"name": "",
"user": "",
"password": ""
}
}
],
"configs": [
{
"key": "object"
}
],
"hostname": "",
"port": 0,
"username": "",
"password": "",
"repository": "",
"repositoryKeyUrl": "",
"enableEnterpriseTrial": false,
"unlimitedJce": false,
"krbAdminUsername": "",
"krbAdminPassword": "",
"javaInstallationStrategy": "",
"license": "",
"billingId": "",
"postCreateScripts": [
""
],
"csds": [
""
]
}
... View more
06-14-2017
04:17 AM
Thanks for the answer! Two questions: it seems that docker build does not have the --net option, only docker run. What can I do to include this setting in the build? What's the supported way of adding/changing a docker image for CDSW? Should I pull it from a repo?
... View more
06-07-2017
02:27 AM
I installed the Data Science Workbench on a gateway node, and it seems that it's all up and running, without any errors. However, for some reason the docker containers do not have access to the internet, so I can't install any packages in them, etc. The exact error message is: Step 2/12 : RUN apt-get update -y
---> Running in 435f1addc906
Err:1 http://security.debian.org testing/updates InRelease
Temporary failure resolving 'security.debian.org'
Err:2 http://deb.debian.org/debian testing InRelease
Temporary failure resolving 'deb.debian.org'
Err:3 http://http.debian.net/debian sid InRelease
Temporary failure resolving 'http.debian.net'
Err:4 http://deb.debian.org/debian testing-updates InRelease
Temporary failure resolving 'deb.debian.org'
Reading package lists...
W: Failed to fetch http://deb.debian.org/debian/dists/testing/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/testing-updates/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://security.debian.org/dists/testing/updates/InRelease Temporary failure resolving 'security.debian.org'
W: Failed to fetch http://http.debian.net/debian/dists/sid/InRelease Temporary failure resolving 'http.debian.net'
W: Some index files failed to download. They have been ignored, or old ones used instead. The output of cdsw status: Cloudera Data Science Workbench Status
Service Status
docker: active
kubelet: active
nfs: active
Checking kernel parameters...
Node Status
NAME STATUS AGE STATEFUL
ip-xx.eu-west-1.compute.internal Ready 15d true
System Pod status
NAME READY STATUS RESTARTS AGE
dummy-2088944543-pfazy 1/1 Running 0 15d
etcd-ip-xx.eu-west-1.compute.internal 1/1 Running 0 15d
kube-apiserver-ip-xx.eu-west-1.compute.internal 1/1 Running 0 15d
kube-controller-manager-ip-xx.eu-west-1.compute.internal 1/1 Running 0 15d
kube-discovery-1150918428-50nmx 1/1 Running 0 15d
kube-dns-3873593988-gg6s2 3/3 Running 0 15d
kube-proxy-0j15p 1/1 Running 0 15d
kube-scheduler-ip-xx.eu-west-1.compute.internal 1/1 Running 0 15d
node-problem-detector-v0.1-ktr13 1/1 Running 0 15d
weave-net-r8j2g 2/2 Running 0 15d
Cloudera Data Science Workbench Pod Status
NAME READY STATUS RESTARTS AGE ROLE
cron-3971587342-ddoca 1/1 Running 0 15d cron
db-4066525870-qchwg 1/1 Running 0 15d db
db-migrate-abec968-oxxek 0/1 Completed 0 15d db-migrate
dhqrwn5eobowq3ea 0/2 Pending 0 4d console
engine-deps-ufifx 1/1 Running 0 15d engine-deps
ingress-controller-2976678207-g88f5 1/1 Running 0 15d ingress-controller
livelog-2494298876-chy37 1/1 Running 0 15d livelog
reconciler-577027981-slrwk 1/1 Running 0 15d reconciler
spark-port-forwarder-7ixp4 1/1 Running 0 15d spark-port-forwarder
web-1304125449-2of76 1/1 Running 2 15d web
web-1304125449-q3rbd 1/1 Running 0 15d web
web-1304125449-vydxd 1/1 Running 1 15d web What do I need to change to have internet access inside the docker containers? Thanks!
... View more
Labels: