Member since
07-25-2017
18
Posts
3
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4123 | 10-20-2017 02:52 PM | |
5686 | 07-26-2017 11:41 AM |
01-16-2019
03:22 AM
To use aes encryption you need to install jce. Be aware also that encryption types on cloudera side should be inline with kerberos server configuration.
... View more
10-23-2018
09:25 AM
Hi Alok, Can you explain how you resolved the SSH key error. Am facing the same issue. Thanks!
... View more
12-14-2017
01:07 AM
Hello I am having the same issue, I get the 3 instances provisioned but I get module.cdh.aws_instance.cdh_cl-instance (remote-exec): [2017-12-14 03:42:55] INFO [pipeline-thread-5] - c.c.l.pipeline.util.PipelineRunner: >> AllocateInstances$GetSuccessfulInstancesAndTerminateFailedInstances/4 [Environment{name='C5-Reference-AWS Environment', provider=InstanceProviderConfig{type='aws'}, crede ...
module.cdh.aws_instance.cdh_cl-instance (remote-exec): [2017-12-14 03:42:55] INFO [pipeline-thread-5] - c.c.l.bootstrap.AllocateInstances: All requested instances failed.
module.cdh.aws_instance.cdh_cl-instance (remote-exec): [2017-12-14 03:42:55] INFO [pipeline-thread-5] - c.c.l.bootstrap.AllocateInstances: Minimum number of instances (1) not available. Terminating available instances (0) as well.
module.cdh.aws_instance.cdh_cl-instance (remote-exec): [2017-12-14 03:42:56] ERROR [pipeline-thread-5] - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed
module.cdh.aws_instance.cdh_cl-instance (remote-exec): com.cloudera.launchpad.pipeline.UnrecoverablePipelineError: Insufficient number of instances available in time 20 MINUTES
module.cdh.aws_instance.cdh_cl-instance (remote-exec): at com.cloudera.launchpad.bootstrap.AllocateInstances$GetSuccessfulInstancesAndTerminateFailedInstances.run(AllocateInstances.java:294) ~[launchpad-bootstrap-1.5.0.jar!/:1.5.0]
module.cdh.aws_instance.cdh_cl-instance (remote-exec): at com.cloudera.launchpad.bootstrap.AllocateInstances$GetSuccessfulInstancesAndTerminateFailedInstances.run(AllocateInstances.java:253) ~[launchpad-bootstrap-1.5.0.jar!/:1.5.0] I set minCount to 1 as with 0 threw me an error as well, I am attempting to do this via a script, if theres no fix yet could you please tell me how to retry via the .conf file as I havent succeded.
... View more
10-26-2017
09:57 AM
include file(...) should work but I believe it requires the full file path. The current latest version of Director (Director 2.6) is on typesafe config version 1.2 which doens't have support for required. You can refer to the following spec to see what's supported in this verison: https://github.com/lightbend/config/blob/v1.2.0/HOCON.md
... View more
09-19-2017
08:12 AM
Hi Tomas79, First, thanks for your contributions to this thread as well as your suggestions! We do steer experienced users toward using configuration files and the bootstrap-remote CLI command vs. the UI, because the UI would get complex if we tried to add a checkbox or field or form for every Director feature into it. The Director server does have a full set of API endpoints that you can use to make updates to clusters that aren't easy or possible to do over the UI, so I recommend taking a look there. If you go to the /api-console URL for Director, there's an interactive facility for learning about the API and trying it out live. For example, there is an API endpoint for importing a configuration file directly into the server. It's documented here: https://www.cloudera.com/documentation/director/latest/topics/director_cluster_config.html#concept_lqt_2y1_x1b We don't have a corresponding configuration file export API endpoint yet, but you are not the first to suggest it, so be assured that it's on our wish list. In the meantime, the API can help you if you're willing to work with that. Director's single log is tough to navigate. Recent Director versions have added more context to lines in the log which make it feasible to filter relevant lines out. We've got some techniques documented here: https://www.cloudera.com/documentation/director/latest/topics/director_troubleshoot.html But I see room for more documentation. Specifically, at least as of 2.4: Each line includes a thread ID in square brackets. The ones starting with "p-" are for pipelines, Director's internal workflows, so you can follow one of those among all the other pipelines and other asynchronous tasks within Director. The fields following the thread ID are the unique (API) request ID, request method, and request URI that ultimately caused the activity being logged. You can work with the logback.xml file for the server to change the formatting, and perhaps even route logging to multiple files for easier comprehension (another ask that we've heard). Again, thanks for your feedback!
... View more