Member since
03-23-2015
1288
Posts
114
Kudos Received
98
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 5201 | 06-11-2020 02:45 PM | |
| 4682 | 04-21-2020 03:38 PM | |
| 3655 | 02-27-2020 05:51 PM | |
| 3661 | 01-23-2020 03:41 AM | |
| 23438 | 01-14-2020 07:14 PM |
11-12-2019
10:48 PM
1 Kudo
Hi @ckk, I believe that we started supporting Sqoop import into S3A since CDH6.1 https://docs.cloudera.com/documentation/enterprise/6/6.1/topics/admin_sqoop_s3_import.html and you need to use "--target-dir". Can you share the full Sqoop command you used when using "--target-dir"? Can you also attach "--verbose" output file for review? Thanks Eric
... View more
11-07-2019
08:43 AM
Exactly I wanted! Thank you @EricL
... View more
11-05-2019
08:21 PM
Hi @wret_1311, Thanks for your response and I appreciate for confirming the solution. I'm glad, it helped you 🙂
... View more
10-31-2019
09:25 PM
Hi @DataMike, Yes, once CM is down, you can't update the configuration unless you "hack" into CM's backend database, which is also down in our scenario. So if you setup MySQL in such a way that CM will connect to LB / VIP host, which will route to the MySQL host that you want to, so in the event of one MySQL instance is down, simply update LB to only go to the working one. This avoids the needs to update the CM config. Hope that can help. Cheers Eric
... View more
10-24-2019
12:08 AM
thanks, i suppose one could just move that to wherever you want the home to be. this was part of a hack deployment, so ultimately not needed.
... View more
10-09-2019
05:32 PM
Yes i didn't notice that it has space. So i used trim for it.
... View more
10-06-2019
03:32 PM
1 Kudo
@Mekaam, Glad that it helped. Cheers Eric
... View more
09-25-2019
04:02 PM
@aohl, Thanks for sharing the details about your resolution on the issue. I am glad that it has been resolved and sure others will benefit from your findings here. Cheers Eric
... View more
09-20-2019
10:04 AM
@Zane- I'm late but can provide some additional insight. I think the suggestion in the error message is a good one (I'm biased because I wrote it, but some thought went into it). "Memory is likely oversubscribed. Reducing query concurrency or configuring admission control may help avoid this error". The general solution for this is to set up admission control with some memory limits so that memory doesn't get oversubscribed, and so that one query can't gobble up more memory than you like. I did a talk at strata that gave pointers on a lot of this things - https://conferences.oreilly.com/strata/strata-ca-2019/public/schedule/detail/73000 In this case you can actually see that query 2f4b5cff11212907:886aa1400000000 is using Total=78.60 GB memory, so that's likely your problem. Impala's resource management is totally permissive out of the box and will happily let queries use up all the resources in the system like this. I didn't see what version you're running, but there were a lot of improvements in this area (config options, OOM-avoidance, diagnostics) in CDH6.1+ There's various other angles you can take to improve this - if the queries using lots of memory are suboptimal, tuning them (maybe just computing stats) makes a big difference. You can also
... View more