This document addresses the specific configuration points that needs to be in place in order to build and store a Hive mestastore outside an EMR cluster in a RDS MySQL database. It also covers the steps to connect a Redshift cluster to an EMR cluster so Redshift can create and access the tables stored within the external metastore.
Resources Used:
• Redshift Cluster
• RDS MySQL Instance
• EMR Cluster
Note: All resources must be in same VPC and same region for this practice.
Creating the RDS MySQL:
1 – First, start creating a RDS MySQL instance if you don’t have one already. Open AWS RDS Console and create an MySQL instance that will be used during this practice.
Note: Please make note of RDS security group, endpoint, Master User and Master Password. We will need that information later on.
2 – Once the RDS MySQL instance is created, modify its security groups to add a rule for All traffic on all Port Range to be allowed from the VPC’s default security group.
Note: This VPC’s default Security Group will be used while creating the EMR cluster later on as well but it needs to be whitelisted beforehand otherwise the EMR launching will fail while trying to reach out to the RDS MySQL.
Before creating the EMR Cluster:
3 – After creating the RDS MySQL (and open its security group to EMR) but right before creating the EMR cluster, a JSON configuration file needs to be created. This file will be ingested by EMR during the bootstrapping phase of EMR’s creation, it will basically tell EMR how to access the remote RDS MySQL database.
4 – Copy the JSON property structure from the following link (use Copy icon): https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hive-metastore-external.html
5 – Paste it in a text editor and modify it carefully with the RDS details you noted earlier.
Note: Be careful, the value property can not contain any spaces or carriage returns. It should appear all on one line. Save it as “hiveConfiguration.json”.
6 – The final JSON configuration file should look like the following:
[
{
“Classification”: “hive-site”,
“Properties”: {
“javax.jdo.option.ConnectionURL”: “jdbc:mysql:\/\/database-1.cefjr3enh3dk.us-east-2.rds.amazonaws.com:3306\/hive?createDatabaseIfNotExist=true“,
“javax.jdo.option.ConnectionDriverName”:”org.mariadb.jdbc.Driver”,
“javax.jdo.option.ConnectionUserName”:”admin“,
“javax.jdo.option.ConnectionPassword”: “*********“
}
}
]
Note 1: replace <hostname>, <username>, <password> with your own details:
Note 2: The part “hive?createDatabaseIfNotExist=true” determines the name of the database to be created in the MySQL RDS, in this case the database will be called “hive”.
7 – After creating above file, upload it to an S3 bucket/folder of your choice (in the same region of your resources).
Creating the EMR:
8 – Now, it is time to create the EMR cluster. To do this, open AWS EMR console and click Create Cluster button. This will prompt the Quick Options page but we won’t be using that. Click on Go to advanced options on the top of the page.
9 – This will send you to the Advanced Options page. There, under Software Configuration, select the following Applications:
Hadoop, Ganglia, Hive, Hue, Tez, Pig, Mahout
10 – In the same page, under Edit Software Settings section, click Load JSON from S3 and select the S3 bucket/path where you uploaded the previous created file “hiveConfiguration.json“. Select the file there and hit Select.
11 – In the Hardware Configuration page, make sure that the EMR cluster is in the same VPC as your MySQL RDS instance. Hit Next if you don’t want to change any Network configuration or Node types.
12 – Hit Next in the General Options page if you don’t want to change anything, although you might want to change the name of your EMR cluster here.
13 – In the next page, Security Options, make sure you have an EC2 Key Pair in that region and select it. Otherwise, create one!
Note: Create one now (if you don’t have one) before creating the EMR as you CAN’T add it later!!!
14 – Still in the Security Options page, expand the EC2 security groups panel and change both, Master and Core & Task instances to use the VPC’s default security group (the same whitelisted in the RDS MySQL security group earlier).
15 – Hit Create cluster and wait the EMR to be created. It will take some time…
Confirming that the metastore was created in the RDS MySQL
16 – Once the EMR is created, another rule needs to be added to the VPC’s default security group, one that allows SSHing into the EMR cluster on port 22 from your local IP. It should look like the following:
17 – With the right rules in place, try to connect to your EMR cluster from your local machine:
– – – chmod 600 article_key.pem
– ssh -i article_key.pem hadoop@ec2-18-XX-XX-XX.us-east-2.compute.amazonaws.com
18 – EMR has a MySQL client installed, use this client to connect to your MySQL database and perform few tests such as if the Security Groups are working properly and if the “hive” database was created properly
Note: You can do a telnet test from within EMR box as well to test Security Group access.
19 – To connect to the RDS MySQL, run the following command from your EMR box:
mysql -h <rds-endpoint> -P 3306 -u <rds master user> -p <rds master password>
Example: mysql -h database-1.cefjr3enh3dk.us-east-2.rds.amazonaws.com -P 3306 -u admin123 -pPwD12345
20 – Once connected, use the following commands to verify if the Hive metastore was indeed created in the RDS. You should be able to see a database named “hive” there:
show databases; à Lists all databases – “hive” should be there
use hive; à Connects you to “hive” database
show tables; à Lists all the meta tables within hive database
select * from TBLS; à Lists all tables created in hive. At this point there’s none
Setting up necessary Spectrum Roles and Network requirements for Redshift and EMR
Note 1: Following steps assume that you already have a Redshift cluster and that you can connect to it. It will not guide you on how to create and access the Redshift cluster.
Note 2: Since EMR, RDS MySQL share the same VPC’s default security group, they should be able to communicate to each other already. If that’s the case, you can skip Step 22 and go straight to Step 23, otherwise, If EMR and Redshift use different security groups, please do the step 22 first.
21 – Create a Role for Spectrum and attach it to your Redshift cluster. Follow the instructions here:
• To Create the Role: https://docs.aws.amazon.com/redshift/latest/dg/c-getting-started-using-spectrum-create-role.html
• To Associate the Role: https://docs.aws.amazon.com/redshift/latest/dg/c-getting-started-using-spectrum-add-role.html
22 – (Optional) Now that Redshift can access S3, Redshift also needs to access EMR cluster and vice-versa. Follow the steps listed under section “Enabling Your Amazon Redshift Cluster to Access Your Amazon EMR Cluster” in the following link: https://docs.aws.amazon.com/redshift/latest/dg/c-spectrum-external-schemas.html#c-spectrum-enabling-emr-access
Note: In summary, this creates an EC2 security group with Redshift’s Security Group and the EMR’s master node’s security groups inside it. Redshift’s Security Group must allow TCP in every port (0 – 65535) while EMR’s Security Group must allow TCP in port 9083 (Hive’s default). Next, you attach this newly created security group to both of your Redshift and EMR clusters.
23 – Once this is done, you should now be able to create the External Schema in Redshift, query the external tables from Redshift and also be able to create/see the schemas/tables from EMR Hive as well. However, at this point there’s no tables created yet.
Creating Tables on Hive First
24 – Log to Hive console and run the following:
> show databases;
default (that’s the only database so far)
> create external table hive_table (col1 int, col2 string)
ROW FORMAT DELIMITED FIELDS TERMINATED BY ‘|’
location ‘s3://<your_bucket>/<your_folder>/‘;
> show tables;
hive_table (that’s the table we just created)
25 – Log back to your MySQL database and run the following commands:
show databases; à Lists all databases – “hive” should be there
use hive; à Connects you to “hive” database
show tables; à Lists all the meta tables within hive database
select * from TBLS; à Lists all tables created in hive, “hive_table” is there!
Note: Now you will be able to see the newly created table “hive_table” showing on your External MySQL catalog.
Creating Schemas and Tables on Redshift Now
26 – On Redshift side, an External Schema must be created first before creating or querying the Hive tables, like following:
CREATE EXTERNAL SCHEMA emr_play à It can be any name, that’s a schema valid only for Redshift.
FROM HIVE METASTORE DATABASE ‘default’ à Use default database to match the database we have in Hive.
URI ‘172.XXX.XXX.XXX‘ PORT 9083 à EMR’s Private IP of the Master Instance. Hive’s default port is 9083.
IAM_ROLE ‘arn:aws:iam::000000000000:role/spectrum‘; à A valid Spectrum Role attached Redshift.
27 – Create the table(s):
create external table emr_play.redshift_table (col1 int, col2 varchar)
ROW FORMAT DELIMITED FIELDS TERMINATED BY ‘|’
location ‘s3://<your_bucket>/<your_folder>/‘;
28 – Simply query the table now:
select * from emr_play.redshift_table;
29 – One more time, log back to your MySQL database and run the following commands again:
show databases; à Lists all databases – “hive” should be there
use hive; à Connects you to “hive” database
show tables; à Lists all the meta tables within hive database
select * from TBLS; à Lists all tables created in hive, both tables are there!
Note: You should be able to see the both Hive and Redshift tables now showing on your External MySQL catalog. You can also query the tables and create new tables on both Hive and Redshift side.
AWS CLOUD DBA 