Hadoop - Connect Spotfire Data Science 6 to HDP 2.3 with HA Namenode and HA Resource Manager (3 Nodes)
Article ID: KB0082683
Updated On:
| Products | Versions |
|---|---|
| Spotfire Data Science | 6.0 |
Description
Connect Spotfire Data Science 6 to HDP 2.3 with HA Namenode and HA Resource Manager (3 Nodes)
Resolution
Connect Spotfire Data Science 6 to HDP 2.3 with HA Namenode and HA Resource Manager (3 Nodes)
Before proceeding with the following steps, follow the standard configuration steps for "Hadoop Data Sources" and "Connect to a Hortonworks Data Source", and then follow these steps.
1. You will need to add these additional configuration parameters:To locate the actual values to each of the properties, you can look in the core-site.xml, hdfs-site.xml, mapred-default.xml.
|
Datasource Parameters |
Datasource Parameter Values |
|---|---|
|
mapreduce.jobhistory.address |
HOSTNAME02.DOMAINNAME:10020 |
|
mapreduce.jobhistory.webapp.address |
HOSTNAME02.DOMAINNAME:19888 |
|
yarn.resourcemanager.admin.address |
HOSTNAME01.DOMAINNAME:8033 |
|
yarn.resourcemanager.resource-tracker.address |
HOSTNAME01.DOMAINNAME:8031 |
|
yarn.resourcemanager.scheduler.address |
HOSTNAME01.DOMAINNAME:8030 |
|
yarn.app.mapreduce.am.staging-dir |
/user |
|
yarn.resourcemanager.hostname.rm1 |
HOSTNAME01.DOMAINNAME |
|
yarn.resourcemanager.hostname.rm2 |
HOSTNAME02.DOMAINNAME |
|
yarn.resourcemanager.webapp.address.rm1 |
HOSTNAME01.DOMAINNAME:8088 |
|
yarn.resourcemanager.webapp.address.rm2 |
HOSTNAME02.DOMAINNAME:8088 |
|
yarn.resourcemanager.cluster-id |
yarn-cluster |
|
yarn.resourcemanager.ha.rm-ids |
rm1,rm2 |
|
dfs.ha.namenodes.<dfs.nameservices> |
nn1,nn2 |
|
dfs.namenode.rpc-address.<dfs.nameservices>.nn1 |
HOSTNAME01.DOMAINNAME:8020 |
|
dfs.namenode.rpc-address.<dfs.nameservices>.nn2 |
HOSTNAME02.DOMAINNAME:8020 |
|
dfs.namenode.http-address.<dfs.nameservices>.nn1 |
HOSTNAME01.DOMAINNAME:50070 |
|
dfs.namenode.http-address.<dfs.nameservices>.nn2 |
HOSTNAME.DOMAINNAME:50070 |
|
fs.defaultFS |
hdfs://<dfs.nameservices> |
|
dfs.nameservices |
<dfs.nameservices> |
|
dfs.client.failover.proxy.provider.<dfs.nameservices> |
org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyPr ovider |
| ha.zookeeper.quorum | HOSTNAME01.DOMAINNAME:2181,HOSTNAME02.DOMAINNAME:2181, HOSTNAME03.DOMAINNAME:2181 |
2. Test the connection and Save when all test results have passed.
Note: If you already have a saved data connection, just add the "web.principal" parameter from the above list.
Issue/Introduction
Feedback
