About sappusamy

sappusamy · ‎10-22-2020

Thanks for the article Santosh. I think we need to update the job definition with kbrokers are argument for the job to run.

sappusamy · ‎09-06-2017

Hi Carter Tez UI doesn't seems to be working with Kerberos cluster. https://issues.apache.org/jira/browse/TEZ-3418 Can you share if any specific procedure to make it work? Also with Tez UI 0.7.0, couldn't find scripts/configs.js file to update timelineBaseUrl and RMWebUrl. Are we referring to /var/www/html/tez-ui/config/configs.env?

sappusamy · ‎08-08-2017

Hi Gayathri, Seems sqoop/hive unable to determine the column delimiter. Can we import the same to HDFS and check the field terminator used in Oracle? We can try the same with option --fields-terminated-by. As the first import was successful, can we check the hive table if data is correctly split into corresponding columns?

sappusamy · ‎06-02-2017

For SmartSense versions 1.3.0 and above, we can use below CLI to regenerate the SSL keys on agents # hst reset-agent

sappusamy · ‎05-15-2017

SmartSense ID is mandatory for starting SmartSense service. This can be created on Hortonworks Support portal under Tools tab if you have an account.

sappusamy · ‎04-11-2017

Hi Jack, Saw a similar issue, when moving away from beeswax page with a running query and trying to get back to it causing timeout. Used restarting HS2 as workaround as well. Was able to address this issue by setting close_queries=true, so HUE doesn't tries to connect to older session thats hung.

sappusamy · ‎04-10-2017

There are 4 options available for SmartSense Server to upload bundles to Hortonworks Datalake, depending on the HDP environment and customer preference. Below are more details about each options and how to configure the same. Option 1: Direct Connection from SmartSense Server SmartSense Server (with embedded Gateway in 1.3.0 and above) having direct connection to Hortonworks Datalake. No additional configurations needed. SmartSense is preconfigured to connect to Datalake via HTTPS protocol Option 2: Dedicated Gateway Server with direct connection When using SmartSense version earlier to 1.3.0, we need a gateway host to be configured to upload bundles. Also in an SmartSense 1.3.0 environment with multiple HDP clusters running, they can be configured to share a dedicated Gateway Server to upload the bundles. If needed the Gateway Server can be located in DMZ area as well. Step 1: Install / Configure SmartSense Gateway Software. To install and configure SmartSense Gateway Software on the Dedicated Gateway Server use the procedures from below links, corresponding to the SmartSense version used. SmartSense 1.2.0 : https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.2.0/bk_smartsense_admin/content/hst_gateway_install.html SmartSense 1.3.0 : https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.3.0/bk_installation/content/gateway_install.html Step 2: Configure SmartSense Server to use the Dedicated Gateway Host Use the below links to configure SmartSense Server, corresponding to versions SmartSense 1.2.0: https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.2.0/bk_smartsense_admin/content/ambari_hst_integrating.html SmartSense 1.3.0 : https://docs.hortonworks.com/HDPDocuments/SS1/SmartSense-1.3.0/bk_installation/content/ambari_gateway_integrating.html Option 3: Embedded Gateway Server via Proxy When the SmartSense Server with Embedded Gateway doesn't have direct connection to Internet, it can be configured to use an existing HTTP / HTTPS Proxy server to reach Hortonworks Datalake Server. Configure /etc/hst/conf/gateway.ini file on the SmartSense Server host as below. ; All proxy configurations are applicable only for HTTPS provider type ; set to true to set up a proxy between gateway and SmartSense environment provider.https.proxy.enabled=true ; fully qualified proxy hostname provider.https.proxy.hostname= mysquid.mydomain.com ; proxy port that will be used by gateway for outbound access provider.https.proxy.port= 3128 ; supported proxy types : HTTP / HTTPS [default:HTTP] provider.https.proxy.type=HTTP ; supported proxy authentication types : NONE / BASIC / DIGEST [default:NONE] provider.https.proxy.auth.type= NONE ; proxy username for identified auth.type provider.https.proxy.auth.username= <proxy_user_name_if_needed> ; proxy password for identified auth.type provider.https.proxy.auth.password= <proxy_user_password> ; [optional] any additional proxy setup parameters ; use "|" to separate multiple parameters ; for example: digest requires parameters such as ; realm=default|nonce=12GHtqeZA!7Ke43 provider.https.proxy.auth.parameters= Also add the following parameter under [gateway] section [gateway] start.validation.enabled=false Option 4: Dedicated Gateway Server via Proxy When the Dedicated Gateway Server doesn't have direct connection to Internet, it can configured to use an existing HTTP / HTTPS Proxy server to reach Hortonworks Datalake server. Configure /etc/hst/conf/gateway.ini file on the Gateway host as below. ; All proxy configurations are applicable only for HTTPS provider type ; set to true to set up a proxy between gateway and SmartSense environment provider.https.proxy.enabled=true ; fully qualified proxy hostname provider.https.proxy.hostname= mysquid.mydomain.com ; proxy port that will be used by gateway for outbound access provider.https.proxy.port= 3128 ; supported proxy types : HTTP / HTTPS [default:HTTP] provider.https.proxy.type=HTTP ; supported proxy authentication types : NONE / BASIC / DIGEST [default:NONE] provider.https.proxy.auth.type= NONE ; proxy username for identified auth.type provider.https.proxy.auth.username= <proxy_user_name_if_needed> ; proxy password for identified auth.type provider.https.proxy.auth.password= <proxy_user_password> ; [optional] any additional proxy setup parameters ; use "|" to separate multiple parameters ; for example: digest requires parameters such as ; realm=default|nonce=12GHtqeZA!7Ke43 provider.https.proxy.auth.parameters= Also add the following parameter under [gateway] section [gateway] start.validation.enabled=false Notes: 1. From SmartSense 1.3.0, SmartSense Gateway uses HTTPS protocol by default. Earlier versions used SFTP protocol. 2. For configuring HTTPS Proxy with HST Gateway, please contact Hortonworks Support to import the Proxy servers SSL certificate.

sappusamy · ‎03-13-2017

Hi Dinesh, SmartSense ID needs to be configured in Ambari - Smartsense Service config page before starting the service. The same can be obtained from support portal under Tools tab.

sappusamy · ‎02-20-2017

KrbHostFQDN should be be set to FQDN of the Hive Server or _HOST in case of multiple HS2 servers. This attribute should not be set to Kerberos server. Could we please update this article to avoid confusions?

sappusamy · ‎12-28-2016

Hi Robert, Can we add steps to stop Ambari server before running ambari-server setup-security and start ambari after selecting option 2? Without restarting Ambari-server, adding KDC admin principal using API method would fail again.

Online	Offline
Last Visited	‎01-27-2021 06:29 PM

Date Registered	‎04-26-2016 01:17 AM
Last Visited	‎01-27-2021 06:29 PM
Total Messages Posted	11
Total Kudos Received	8

Re: Spark Streaming in CDE with Stream Messasing M...

Re: How to install Tez UI Standalone and use it to...

Re: Sqoop Incremental update with Merge-key failin...

Re: How to turn off 2 way SSL authentication for s...

Re: Is there a way to try SmartSense without regis...

Re: Hue connects hiveserver2 timeout in hortonwork...

How to configure SmartSense Gateway to upload bund...

Re: Error setting up HST Server while trying to ad...

Re: Hive ODBC Setup with UnixODBC and Debug Loggin...

Re: Adding KDC Administrator Credentials to the Am...