Member since
09-29-2015
30
Posts
16
Kudos Received
5
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
6022 | 12-26-2016 10:50 PM | |
5101 | 12-22-2016 11:36 PM | |
27677 | 12-15-2016 10:59 AM | |
3193 | 09-27-2016 01:04 AM | |
6751 | 09-20-2016 06:39 AM |
05-03-2017
11:53 AM
1 Kudo
This is fixed in Hortonworks Cloud. Is this on-prime cluster or Hortonworks Cloud?.
... View more
03-20-2017
03:57 AM
Can you share the details of the HDP/HDC version used and the s3a connector version being used?. If it is recent versions you can enable "fs.s3a.experimental.input.fadvise=random" for ORC dataset, which reduces the number of connection establishments and breakages to S3. Not sure if you are using EC2 instances or on-prem for accessing S3. But in case the machine itself has network connectivity issues to S3, easiest option could be to eliminate that node or fix the n/w inconsistency.
... View more
03-20-2017
03:52 AM
>>> 2017-03-18 22:43:27,002 [PigTezLauncher-0] INFO org.apache.hadoop.yarn.client.api.impl.YarnClientImpl - Submitted application application_1489855879213_0002
2017-03-18 22:43:27,005 [PigTezLauncher-0] INFO org.apache.tez.client.TezClient - The url to track the Tez Session: http://pc-1.thenet.edu:8088/proxy/application_1489855879213_0002/
>>> I agree with zyang. Looking at the logs, it appears that there isn't enough capacity to launch. Can you verify the queue configs and cluster capacity?
... View more
02-10-2017
12:39 AM
Stack trace points to "s3native.NativeS3FileSystem" which is pretty much deprecated. Suggest to use "s3a://" in table location "(show create table ex_httpvendorstats" would reveal the details)
... View more
02-03-2017
05:06 AM
@PJ - Would it be possible to share the hive.log when you observed this?
... View more
02-03-2017
04:42 AM
Can you please check if "hive.mv.files.thread=0" helps in this case?
... View more
01-12-2017
04:02 PM
2 Kudos
You can remove "hive.tez.java.opts=-Xmx4096m". Tez automatically takes up 80% of the container size allocated to it. As per your hive-site.xml and yarn-site.xml, "hive.tez.container.size=6144", "yarn.scheduler.minimum-allocation-mb=6144". So ~4915MB should be automatically be assigned without specifying any Xmx value in hive.tez.java.opts. Remove "--hiveconf hive.tez.container.size=2048" from hive cli command. By specifying 2048, it would end up under utilizing the memory. After incorporating #1, with the current config in hive-site, yarn-site you have posted, can you run "hive" cli without specifying any option and run the query? For simple like select count(*) from table, it should not launch tez job if it had enough information about the rows in metastore. Run "analyze table tweets compute statistics" and re-run this select count(*) statement. It should fetch information from metastore directly as opposed to launching the tez job.
... View more
01-10-2017
03:40 PM
For beeline, can you "set hive.llap.client.consistent.splits=false;" and run your query.
... View more
12-26-2016
10:50 PM
2 Kudos
S3N is really old and pretty much deprecated. Can you change your URL to "s3a://santhosh.aws.com/tmp" and ensure that you have "fs.s3a.impl=org.apache.hadoop.fs.s3a.S3AFileSystem". If you do not have InstanceProfileCredentialProvider, you have to configure "fs.s3a.access.key and fs.s3a.secret.key".
... View more
12-22-2016
11:36 PM
1 Kudo
You can edit spark configs in ambari and add the following lines. - Restart spark/zeppelin services. - Run a simple query in S3 via zeppelin notebook - Note down the yarn application launched for Zeppelin ("yarn top" from cli) can help identify that. - S3 debug messages would be available in the yarn logs. You might have to stop zeppelin for the app to finish and ensure you have permission to view yarn logs via "yarn logs -applicationId <appId>" for this application. e.g messages 16/12/22 23:30:25 DEBUG AmazonWebServiceClient: Internal logging succesfully configured to commons logger: true
16/12/22 23:30:25 DEBUG AwsSdkMetrics: Admin mbean registered under com.amazonaws.management:type=AwsSdkMetrics ... 16/12/22 23:30:26 DEBUG requestId: x-amzn-RequestId: not available
16/12/22 23:30:26 DEBUG request: Received successful response: 200, AWS Request ID:...
... View more