About arunpoy

bleonhardi · ‎06-29-2016

Depends on your processing. Can you send the query. Phoenix DOES push down local aggregations in the server side but does the full aggregation in the client. ( Like a Combiner ( Regionserver ) -> Reducer ( Client ) pattern.) One way to fix this can be salting of the keys to make sure specific keys are only in specific region servers. For example if you have 100 regions and 100 group by keys, he will have to copy 100x100 rows to the client and merge them there. However if you make sure that each key is only present in one Region through salting he would only have to pull up 100x1 key. But your query would help.

ssubhas · ‎06-28-2016

@ARUNKUMAR RAMASAMY The jars need to be present on the Hiveserver machine. It is not necessary to have them on all the nodes. You can refer to below link: http://stackoverflow.com/questions/31802908/adding-hive-jars-permanently/31808016 Thanks and Regards, Sindhu

arunpoy · ‎06-27-2016

Thanks @Jitendra Yadav and @Sindhu, seems this feature of importing directly to a phoenix table is not available till sqoop 1.4.7 gets released.

deepesh1 · ‎06-27-2016

HiveServer2 instance registers itself to Zookeeper under the /hiveserver2 node.

yjagadeesan · ‎06-23-2016

Go with the recommendations above as @Jitendra Yadav has recommended.

ewalk · ‎06-21-2016

I generally recommend letting DNS handle this. The latest versions of the KRB client will default to resolving the KDC from SRV records in the DNS for the realm. This should be configured by default if you use Microsoft Active Directory (or AWS Simple AD). If you want it explicit in your krb5.conf file, you can use DNS round robin with the A/AAA/CNAME and reference that name in krb5.conf. Further, you could have multiple "kdc" entries for a realm in krb5.conf and a master_kdc entry which is only used when there are certain kinds of issues. You can always manage the krb5.conf from Ambari inside the Kerberos component configs.

rchaman · ‎02-17-2017

Check if you can listen to the mysql port. [root@node1 ~]# lsof -i :3306 #replace the port no as applicable If there is no output that means mysql is running in "skip_networking" mode. Disable the mode by commenting out below line in /etc/my.cnf and restart the db # Don't listen on a TCP/IP port at all. #skip-networking Now check the port again . It should show similar output COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME mysqld 18730 mysql 10u IPv4 120579417 0t0 TCP *:mysql (LISTEN) mysqld 18730 mysql 29u IPv4 120579424 0t0 TCP localhost:mysql->localhost:41107 (ESTABLISHED) Now try to run sqoop job.

arunpoy · ‎06-21-2016

@Predrag Minovic It helped, thanks a lot

arunpoy · ‎06-02-2016

Thanks Jitendra. It helped

pankaj_singh · ‎06-21-2016

@ARUNKUMAR RAMASAMY By de-register you mean "uninstall/destroy the cluster" ?

Online	Offline
Last Visited	‎03-14-2019 05:48 AM

Member Since	‎01-21-2016 11:26 AM
Last Visited	‎03-14-2019 05:48 AM
Posts	290
Kudos received	76

Cloudera Community

Re: Dead region server showing on ambari even afte...

Re: Zeppelin phoenix error

Re: job history not available

Re: Pushing down Phoenix quey

Re: hive auxillary jars

Re: sqoop import to a phoenix table

Re: beeline error

Re: Data node down

Re: Kerberos KDC secondary

Re: Sqoop import

Re: ambari database maintenance

Re: HDP_VERSION

Re: Deregister an ambari blueprint