Member since
01-28-2016
9
Posts
1
Kudos Received
0
Solutions
11-08-2016
02:46 PM
I experienced this issue when setting the parameter associatePublicIpAddresses: false The default seems to be 'true'. The notes for this parameter say ... # Whether to associate a public IP address with instances or not. If this is false # we expect instances to be able to access the internet using a NAT instance # # Currently the only way to get optimal S3 data transfer performance is to assign # public IP addresses to your instances and not use NAT (public subnet type of setup) # # See: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html So it makes sense that if you attempt to set this parameter to false that you may need to configure NAT as mentioned above.
... View more
02-04-2016
08:04 PM
Thanks; our incoming CIDR's were incorrect.
... View more
02-04-2016
04:13 PM
1 Kudo
The underlying cause of the failure seems to be a failure to start Kafla: [2016-02-01 19:10:58] ERROR [pipeline-thread-35] - c.c.l.b.UnboundedWaitForApiCommand: Command Start with ID 72 failed. Details: ApiCommand{id=72, name=Start, startTime=Mon Feb 01 19:10:10 EST 2016, endTime=Mon Feb 01 19:10:10 EST 2016, active=false, success=false, resultMessage=Failed to start service., serviceRef=ApiServiceRef{peerName=null, clusterName=Atlas-Test, serviceName=CD-KAFKA-MnViYSKk}, roleRef=null, hostRef=null, parent=null} Cloudera Manager command execution history should have more details. I believe get this error because the Kafka parcel is not distributed (as you know Kafka is not included in the CDH parcel). Please add "KAFKA: 0.8.2" to the products {} block. You may also need to add reference to the precise parcel repositories you want to use.
... View more
01-31-2016
02:51 PM
I meant to ask, is there any plans for amazon linux support in the future?
... View more