09-21-2015 07:19 AM - edited 09-21-2015 07:20 AM
I'm using Cloudera Director client to stand up the cluster and intermittently the process is hanging after the manager has been created and the new isnstances have been requested.
The last log message is
Requesting 9 instance(s) in 5 group(s) ...
When I go to AWS management console I see that the instances have been requested by that a number of them apparently haven't been named. I'm not sure if this stops CD from being able to connect to them, but as far as AWS is concerned they're fully up.
Is this a known issue with a workaround by any chance?
09-21-2015 01:11 PM
Amazon had an outage on Sept 20th in the N. Virginia (us-east) region. Could you confirm if your instances were within this region? If yes, does it work smoothly again when you retry it?
If you continue to see failures, here are a couple things to check:
a) When this problem happens, in the AWS console are all the instances marked 'running', and are all the status checks passing?
b) Since you are using a configuration file with the Director client, could you try running this command to validate the file? "cloudera-director validate <conf file>"
If the above check passes and you still hit these failures, could you provide the following information to us (after removing any credentials or other private data from the files)
09-21-2015 01:37 PM