Member since
04-09-2019
254
Posts
140
Kudos Received
34
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1725 | 05-22-2018 08:32 PM | |
11546 | 03-15-2018 02:28 AM | |
3121 | 08-07-2017 07:23 PM | |
3935 | 07-27-2017 05:22 PM | |
2138 | 07-27-2017 05:16 PM |
07-20-2017
06:09 PM
@Vishwanath Voruganti Please share the output of the "klist -kte <new-keytab>" here, so that I can see the current key encryptions types. That is, if you still have the keytab lying around. Yes, this is the issue because of encryption type mismatch.
... View more
07-19-2017
09:04 PM
Hello @Vishwanath Voruganti, What is happening is this: 1. When Solr is starting up, it is trying to authenticate to AD using solr.service_nn.keytab. 2. During authentication, AD server responds back to Solr which is encrypted with RC4-HMAC encryption (default for AD) 3. Solr is trying to decrypt this response using keytab (which has key only for AES128 encryption). 4. Hence Solr is not able to get authenticated with AD and is giving the error - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC The quickest way to solve this problem is to generate a keytab in AD for "sorl/nn.wwtest.net" with RC4-HMAC encryption and use the same on Solr node. Hope this helps. PS - I don't understand why you used "solr.service_nn.keytab" in configuration but listed "solr.service_dn1.keytab" in command output.
... View more
07-19-2017
08:45 PM
2 Kudos
Hello @Micaël Dias, HTTP authentication (to be specific SPNEGO authentication) works in two-pass handshake mechanism. First, when client approaches HTTP server, the server would check the request header and respond by sending 401 'Authentication required' message. We see this response as first log in access log. 192.168.0.1 - - [17/Jul/2017:14:11:42 +0000] "GET /service/assets/accessAudit?page=0&pageSize=25&total_pages=66&totalCount=1626☆tIndex=0&sortBy=eventTime☆tDate=07%2F17%2F2017 HTTP/1.1" 401 1113 To this, the client would again send Negotiate header (indicating the Kerberos authentication token) to server. If everything works out, then server would respond with 200 OK message. 192.168.0.1 - - [17/Jul/2017:14:11:43 +0000] "GET /service/assets/accessAudit?page=0&pageSize=25&total_pages=66&totalCount=1626☆tIndex=0&sortBy=eventTime☆tDate=07%2F17%2F2017 HTTP/1.1" 200 11187 This is totally normal and expected when authentication is enabled for HTTP server. Hope this helps !
... View more
06-29-2017
06:31 PM
1 Kudo
Great news !!!!
... View more
06-07-2017
10:37 PM
1 Kudo
@vsubramanian, I'm afraid this is currently not possible. The only WebHDFS REST api that implements "recursive" query parameter is delete. So if you use recursive with delete, that would work. The ListStatus API here has not implemented any recursive logic. For your use-case, you'll manually need to call curl with op=LISTSTATUS multiple times for each directory after parsing the output. Similar to what "ls -R" Shell command does currently. Hope this helps.
... View more
06-05-2017
10:48 PM
When you say "I want to make hadoop read the configuration file again..", do you mean Namenode service or any other service? Could you please clarify which service you want to refresh. Thanks.
... View more
06-03-2017
08:14 PM
Pretty informative and useful. Thanks @Dominika Bialek for writing this. Keep it up !!
... View more
06-02-2017
01:52 AM
4 Kudos
Unlike other services, Knox doesn't expose Java Heap settings via Ambari. Follow these steps to change default Heap settings for Knox: 1. On the Knox node, login as root and go to this directory: /usr/hdp/current/knox-server/bin # cd /usr/hdp/current/knox-server/bin 2. Make a copy of the file that we are going to change next. # cp gateway.sh gateway.sh.backup.`date +%m%d%Y-%H-%M-%S` 3. Open gateway.sh in text editor and change this line: APP_MEM_OPTS=""
to this:
APP_MEM_OPTS="-Xmx5g -XX:NewSize=3G -XX:MaxNewSize=3G -verbose:gc -XX:ParallelGCThreads=8 -XX:+UseConcMarkSweepGC -Xloggc:/var/log/knox/knox-gc.log -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps"
Shown above are the example values for Knox Heap. This should be updated based on user's environment. General formula for Knox Heap size will be: Recommended KNOX Heap Size =
(Webhdfs(ConcNumOfRequest*(replayBufferSize)) +
HBase(ConcNumOfRequest*(replayBufferSize)) +
Hive(ConcNumOfRequest*(replayBufferSize))) + 20 % for request surges where: ConcNumOfRequest = Number of concurrent requests expected for each component (WebHDFS, HBase, Hive etc.) replayBufferSize = Size of the largest incoming request to Knox Based on the Heap size value, user need to further tune the NewSize and MaxNewSize. 4. Save changes to gateway.sh and restart Knox via Ambari. Confirm the new settings via 'ps -ef | grep knox' command. # ps -ef| grep gateway
knox 29236 1 93 23:18 ? 00:00:29 /usr/jdk64/jdk1.8.0_77/bin/java -Xmx5g -XX:NewSize=3G -XX:MaxNewSize=3G -verbose:gc -XX:ParallelGCThreads=8 -XX:+UseConcMarkSweepGC -Xloggc:/var/log/knox/knox-gc.log -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -jar /usr/hdp/current/knox-server/bin/gateway.jar
... View more
Labels:
06-01-2017
08:39 PM
Nice and descriptive article @spolavarapu, keep it up !!!
... View more
05-28-2017
11:52 AM
Thanks @rguruvannagari for the mention. That pushed me to write my pending article. I cover the new LDAP/AD options available in Apache Zeppelin 0.7.0 / HDP 2.6 in this article. Please check.
... View more