Member since
09-29-2015
25
Posts
7
Kudos Received
6
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
923 | 03-23-2018 04:18 PM | |
570 | 12-11-2017 06:37 PM | |
1742 | 07-17-2017 10:10 PM | |
548 | 05-11-2017 06:22 PM | |
3924 | 05-03-2017 06:08 PM |
10-03-2018
06:03 PM
Pls refer documents : https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.5.0/installation-hdp/content/ss_installing_smartsense_with_ambari.html
... View more
10-02-2018
06:47 PM
Can you pls retry ? I was able to access to and download the rpm from this link : http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.7.1.0/smartsense/smartsense-hst-1.5.0.2.7.1.0-169.x86_64.rpm Try to manually curl to this url.
... View more
09-13-2018
06:44 PM
It is recommended that the RPC handler count is set to 20 * log2(Cluster Size) with an upper limit of 200. Refer more details here : https://community.hortonworks.com/articles/43839/scaling-the-hdfs-namenode-part-2.html
... View more
03-23-2018
04:18 PM
1 Kudo
@Joe Walton, SmartSense Gateway does not support NTLM auth. NTLM is Microsoft proprietary. Gateway supports BASIC and DIGEST for proxy authentication. We can provide assistance if you can have one of the supported auth methods.
... View more
12-27-2017
08:26 PM
Affected versions: 1.4.0, 1.4.1, 1.4.2, 1.4.3 Symptoms: A Bundle is available in Datalake but
the status is still Upload Failed. Following error is reported in the
hst-server.log. 2017-09-08 17:44:09,319 ERROR [pool-1-thread-1] UploadRunnable:236 -
Error occurred during upload bundlecom.hortonworks.support.tools.server.SystemException:
java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1
column 10 at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:182) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at com.hortonworks.support.tools.gateway.UploadRunnable.retryUploadBundle(UploadRunnable.java:201) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:176) at
com.hortonworks.support.tools.gateway.UploadRunnable.run(UploadRunnable.java:224) at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at
java.util.concurrent.FutureTask.run(FutureTask.java:266) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at
java.lang.Thread.run(Thread.java:745)Caused by:
com.hortonworks.smartsense.gateway.client.GatewayClientException:
java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1
column 10 at
com.hortonworks.smartsense.gateway.client.GatewayHttpsClient.uploadBundle(GatewayHttpsClient.java:246) at
com.hortonworks.support.tools.gateway.UploadRunnable.uploadBundle(UploadRunnable.java:125) ... 26 moreCaused by: com.google.gson.JsonSyntaxException:
java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1
column 10 at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176) at
com.google.gson.Gson.fromJson(Gson.java:795) at
com.google.gson.Gson.fromJson(Gson.java:761) at
com.google.gson.Gson.fromJson(Gson.java:710) at com.google.gson.Gson.fromJson(Gson.java:682) at
com.hortonworks.smartsense.gateway.client.AGatewayClient.populateResponse(AGatewayClient.java:43) at
com.hortonworks.smartsense.gateway.client.GatewayHttpsClient.uploadBundle(GatewayHttpsClient.java:230) ... 27 moreCaused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but
was STRING at line 1 column 10 at
com.google.gson.stream.JsonReader.expect(JsonReader.java:339) at
com.google.gson.stream.JsonReader.beginObject(JsonReader.java:322) at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:165) ... 33 more Reason: This happens due to
incompatibility of HST Server and HST Gateway versions. The upload response format sent by
Hortonworks SmartSense Datalake Upload Service is updated in 1.4.x. HST Server
expects are particular format of the response from the Upload Service. HST
Server 1.4.x required HST Gateway 1.4.x to provide the right response. Solution: Verify the installed hst version
on HST Server node and the Gateway Node. Command : hst --version If SMARTSENSE-HST rpm version on
Gateway is lower than HST Server, then it has to be upgraded. HST Gateway is
backward compatible with HST Server.
... View more
Labels:
12-11-2017
06:37 PM
1 Kudo
@Jorge Luis Hernandez Olmos, We have seen this happen in some versions. There are some Tez analyzers that consume a lot of resources. Do this config change to disable the analyzers that consume more resources. Disabling these does not impact your normal processing or analysis. Ambari > SmartSenseConfigs> custom activity-conf :
tez_job.activity.analyzers= com.hortonworks.smartsense.activity.job.tez.analyzer.SlowNodeAnalyzer, com.hortonworks.smartsense.activity.job.tez.analyzer.LocalityAnalyzer, com.hortonworks.smartsense.activity.job.tez.analyzer.SkewAnalyzer, com.hortonworks.smartsense.activity.job.tez.analyzer.SlowestVertexAnalyzer, com.hortonworks.smartsense.activity.job.tez.analyzer.SpillAnalyzer This disables ContainerReuseAnalyzer, SlowTaskIdentifier, CriticalPathAnalyzerandShuffleTimeAnalyzer. Pls note, by default activity analysis consumes minimum of 8 GB of heap even if above analyzers are disabled. So, it is ok to see such consumption even after disabling these tez analyzers.
... View more
11-10-2017
03:52 PM
@Pravin Bhagade, Pls check /var/log/smartsense-activity/activity-analyzer.log for possible failures. All these tables are created when you run analyzer for the first time. Try if you can resolve the root cause, otherwise set this property and restart analyzer to drop and re-create the tables. Advanced > Custom activity-analyzer-conf phoenix.setup.drop.existing.tables=true NOTE : this will drop and recreate tables every time you restart analyzer. So, set it to false once they are created. Also, placement of analyzers is important : https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.4.3/bk_installation/content/activity_analyzer_placement.html
... View more
07-17-2017
10:10 PM
@Karan Alang Please try removing /var/lib/smartsense/hst-server/updates/upload/patch first and restart hst server and agents. If you still get the same error the try the same by removing /var/lib/smartsense/hst-server/updates/upload and restart.
... View more
05-11-2017
06:22 PM
2 Kudos
@Saurabh B You can have multiple Activity Analyzers. So , install and start a another Activity Analyzer on the new node. You will see Activity Analyzer in the add components in Ambari. You can stop and remove the earlier Analyzer once the new Analyzer setup is completed.
... View more
05-03-2017
07:26 PM
@Bruce Perezthen try /var/run/smartsense-activity-explorer/activity-explorer.pid
... View more