Member since
05-16-2016
785
Posts
114
Kudos Received
39
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2326 | 06-12-2019 09:27 AM | |
| 3568 | 05-27-2019 08:29 AM | |
| 5721 | 05-27-2018 08:49 AM | |
| 5237 | 05-05-2018 10:47 PM | |
| 3113 | 05-05-2018 07:32 AM |
12-06-2018
01:33 PM
1 Kudo
Yes we only tried deleting the out-of-sync partition. It did not work. After a lot of research we came to a conclusion to increase replica.lag.time.max.ms to 8 days. As its been around 8 days that a few replicas were out of sync. This resolved our issue and while it took a few hours for followers to fetch and replicate the 7 days of data. https://www.confluent.io/blog/hands-free-kafka-replication-a-lesson-in-operational-simplicity/ helped to understand the ISR's
... View more
11-30-2018
02:22 AM
I use the below trick in shell scripts for known queries that don't have an impact if killed. I call the impala-shell from bash/cron using the below line timeout 600 impala-shell -i $IMPALA_ADDRESS -q "compute stats hive_db.table_name;" The all important part is "timeout 600" which will end the session after 10 mins.
... View more
11-04-2018
11:30 PM
This is the solution for the above question hive> select a.mon,a.no,b.no from t13 a join t14 b on (a.mon = b.mon);
Query ID = tester_20181105125833_11998cc2-0343-4f56-9e85-2f4628e72e2b
Total jobs = 1
Launching Job 1 out of 1
Status: Running (Executing on YARN cluster with App id application_1541140095101_0005)
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 .......... SUCCEEDED 1 1 0 0 0 0
Map 2 .......... SUCCEEDED 1 1 0 0 0 0
--------------------------------------------------------------------------------
VERTICES: 02/02 [==========================>>] 100% ELAPSED TIME: 0.48 s
--------------------------------------------------------------------------------
OK
JAN 447 547
FEB 504 497
MAR 554 544
APR 517 526
MAY 456 524
JUN 468 527
JUL 528 540
AUG 509 500
SEP 483 490
OCT 565 564
NOV 561 530
DEC 538 452
Time taken: 1.315 seconds, Fetched: 12 row(s)
... View more
10-26-2018
06:57 AM
Hi, actually both session and operation timeouts are set to 6h, so this shouldn't be a problem. Thanks!
... View more
10-24-2018
10:17 PM
@Huriye: What does that mean ? Please can you explain....
... View more
10-18-2018
06:57 AM
How can i login to a master node of cluster via terminal ??? I looked for it every where but it made me more confuse. I appreciate your help. Thanks, Roshan
... View more
10-04-2018
03:57 AM
thanks guna. really appreciated with your quick response. While trying the same, noted the following issues 1. if there are multiple columns to export, then each column is being separated by | symbol as well (along with comma), which was unable to remove 2. the table data exported into multiple splits files, but the expected output is a single file. 3. if any one of the tag values are null, which are not being shown in the output do you have any thoughts on this? how to handle these issue?
... View more
09-30-2018
01:44 AM
1 Kudo
Hi, You are using wrong connection string. Use: jdbc:hive2://localhost:10000/ Thanks, Bhavesh
... View more
09-28-2018
01:03 PM
HI, I Have downloaded clodera quickstart 5.13.x and allocated 9 gb ram and 2 processors Still i am facing hangout issue when i am open cloudera manager, Could you please help on this issue Thanks, Madhan
... View more
09-25-2018
07:45 PM
@mdjedaini There is nothing to do with cloudera on this request as there are so many other tools are available in the market. I am not sure how big your environment. In general, those who are using big environments with huge nodes will use some tools like Chef, Puppet, Terraform, Ansible, etc to achieve your requirement (for cloud there are another different set of tools like Cloudformation, etc) In high level, you can divide them into two category: Push and Pull based a. Tools like Puppet and Chef are pull based. Agent/Client on the server periodically checks for the configuration information from central server(master) b. Ansible is Push based. Central server pushes the configuration information on target servers. You control when the changes are made on the servers
... View more