I tried using --hs2-url but got the below error 'ERROR tool.BaseSqoopTool: Error parsing arguments for import:  ERROR tool.BaseSqoopTool: Unrecognized argument: --hs2-url' Sqoop command: sqoop import \ --connect $MYCONN \ --username $MYUSER \ --password $MYPSWD \ --table "employees_test" \ --target-dir "/user/username/importdir/employees_test" \ --delete-target-dir \ --hive-import \ --hs2-url "jdbc:hive2://hs2host1:2181,hs2host2:2181,hs2host3:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2;ssl=true;sslTrustStore=/etc/cdep-ssl-conf/CA_STANDARD/truststore.jks;trustStorePassword=password" \ --hive-database 'test' \ --hive-table 'batch' ... View more

Hello @PabitraDas  Sorry for the late reply, I tested this configuration for having 3 partitions of 2 TB space in the new nodes, like /hdp/hdfs01, /hdp/hdfs02, /hdp/hdfs03 but when I added the nodes to the cluster I saw it create directories under /hdp for other partitions as well eg., /hdp/hdfs04 - /hdp/hdfs09 like in the other old Datanodes, where /hdp is in root partition. I believe it had created these directories from HDFS configs where the DN directories are /hdp/hdfs01 - /hdp/hdfs09 ... View more

Hello @nthomas , Please correct me if i'm wrong:  AD domain : abc.example.com HDP DEV domain: dev.xyz.example.com HDP PROD domain: xyz.example.com   In DEV Kerberos settings: Realm Name : ABC.EXAMPLE.COM KDC Host : ldapserver.abc.example.com:636 Domains: .dev.xyz.example.com,dev.xyz.example.com   In Prod Kerberos settings: Realm Name : ABC.EXAMPLE.COM KDC Host : ldapserver.abc.example.com:636 Domains: .xyz.example.com,xyz.example.com   ... View more

@nthomas thank you for your reply. So my configuration would be: Realm Name: ABC.EXAMPLE.COM domain_realm: .example.com = EXAMPLE.COM example.com = EXAMPLE.COM this configuration will map all my hdp nodes to this Realm correct? All my hdp nodes (EST) should be in sync with Ldap server (UTC) ... View more