Help with Cloudera Live on AWS

[#1]

I am trying to install Cloudera live on AWS with Tableau. The stack creation is complete.  I see 6 instances running on my account.  I did not receive any email with instructuctions on how to access Cloudera.  Can someone suggest how I can check if the installation is complete

Mark

[#2 · Accepted solution]

Glad it's working. You should make the rules as specific or as general as
your needs dictate. I had forgotten about the rule that allowed all
outbound traffic, simply so any request originating in the cluster would
succeed (since the ephemeral ports for Linux are allowed inbound traffic).
The default firewall is quite strict about incoming traffic...

[#3]

Hi Sean,

Thanks for the input.  I am not good with networking and I would like to first see if I can connect from my machine to the cluster to run reports.  I would like to try with what your are saying here:

"If you don't really care about the security of your cluster, you can also try just opening up the network ACL entirely to see if everything else is working
before trying to lock it down again"

Can you tell me how I can do this?  I will test out connectivity and then lock it down.

Please let me know when you get a chance.

Mark

[#4]

All traffic is denied by default, so add a rule to the existing rules that
is set to 'ALLOW', set to apply to 'All traffic' / all ports, and set the
source / destination IP to 0.0.0.0/0 (which means all). Do this on both the
inbound rules tab, and the outbound rules tab.

[#5]

Hi Sean,

I can now connect through Microstrategy.  Currently, the network is open to all traffic.  I am going to try the secure option next.  I have downloaded and installed Wireshark. Thanks very much for your help.

Mark

[#6]

Hi Sean,

All I had to do is to add an entry for inbound (custom tcp - port 21050) and I added ip as 0.0.0.0/0.  This works.  The outbound already has an entry to allow all traffic from all ip addresses and ports.  Do you want me to modify outbound entry to make it very specific?  I am not going to change the outbound defaults.

Please reply when you get a chance.

Mark

[#7 · Accepted solution]

Glad it's working. You should make the rules as specific or as general as
your needs dictate. I had forgotten about the rule that allowed all
outbound traffic, simply so any request originating in the cluster would
succeed (since the ephemeral ports for Linux are allowed inbound traffic).
The default firewall is quite strict about incoming traffic...

[#8]

Thanks Sean.  I am closing this case.

Mark

[#9]

Hi Sean,

I am exploring data in the tables and I see order_date as a bigint column in orders table.  When I tried to convert using the function, I don't get the right date format.  I am assuming this is the right function to use. 

select from_unixtime(order_date,"yyyy-MM-dd HH:mm:ss.SSSS")from orders

When I run this query, I get data such as

45533-04-18 12:00:00.0000

Please see in my instance and let me know if I am using the right function.

Mark

[#10]

The timestamps (e.g. 1374735600000) appear to be in milliseconds. That
function expects timestamps to be in seconds. The documentation for such
functions is here:
http://www.cloudera.com/content/www/en-us/documentation/archive/impala/2-x/2-1-x/topics/impala_datet...
Not sure what function to work best: there are others that refer to UTC
timestamps instead of UNIX timestamps, but I'm not sure of the details
there. The Impala forum might be a better place to ask for some pointers.
Another option to investigate might be transferring the data into another
table and converting those values to be in seconds.

[#11]

Hi Sean,

I am able to make changes by adding additional columns for date conversion.  It works as designed on the server.  But, for some reason, I am not able to access the new columns from microstrategy.  I also tried to access from a query tool and still the new columns do not show up.  Can you provide any possible reason for the new columns to not show up from the client?

I am thinking of opening a new case as this is a different issue but I could not find the link to create one.

Mark

[#12]

Hi Sean,

I resolved the issue with new columns not showing up on the client.  I had to restart Hive and Impala servers.  Now everything shows up. 

I dont have any other issues currently.  Thanks for your help.

Mark