Member since
01-19-2017
3679
Posts
632
Kudos Received
372
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 927 | 06-04-2025 11:36 PM | |
| 1529 | 03-23-2025 05:23 AM | |
| 757 | 03-17-2025 10:18 AM | |
| 2728 | 03-05-2025 01:34 PM | |
| 1808 | 03-03-2025 01:09 PM |
01-16-2019
06:07 PM
@Adam J In reality, Kubernetes is an orchestration tool downloadable from kubernetes and then download a nifi as a docker image from docker hub. Have a look at this preconfigured kubernetes-nifi cluster HTH
... View more
01-16-2019
05:17 PM
1 Kudo
@Javert Kirilov I just run the command against a kerberized 2.6.5 and all is okay $ curl --negotiate -u : http://panda:50070/webhdfs/v1/tmp?op=GETFILESTATUS
{"FileStatus":{"accessTime":0,"blockSize":0,"childrenNum":7,"fileId":16386,"group":"hdfs","length":0,"modificationTime":1539249388688,"owner":"hdfs","pathSuffix":"","permission":"777","replication":0,"storagePolicy":0,"type":"DIRECTORY"}} Let me spin up an HDP 3.x matching your spec then kerberize it and will revert. are you using Active Directory Kerberos authentication
... View more
01-16-2019
11:57 AM
1 Kudo
@huzaira bashir There seems to be a mismatch between the Active Directory encryption type and the MIT encryption types can you align the 2 supported_enctypes to be the same. Windows supports the below encryption types depending on the Windows version which are weak encryption DES_CBC_CRC
DES_CBC_MD5
RC4_HMAC_MD5
AES128_HMAC_SHA1
AES256_HMAC_SHA1 In your kdc.conf you have stronger encryption types you validate the AD encryption types? Else try to comment out the kdc.conf encryptions see below # supported_enctypes = aes256-cts:normal aes128-cts:normal des3-hmac-sha1:normal arcfour-hmac:normal camellia256-cts:normal camellia128-cts:normal des-hmac-sha1:normal des-cbc-md5:normal des-cbc-crc:normal and see whether the error persists?
... View more
01-16-2019
08:31 AM
@huzaira bashir Can you share your krb5 and kdc conf files for analysis?
... View more
01-15-2019
03:51 PM
@Javert Kirilov Have you encountered a Kerberos issue? Is it similar to the thread opened by Bashir? It's usually good to open a new thread as this one isn't being actively viewed. I will be happy to help you if you attached some logs ,screenshot and some error logs
... View more
01-14-2019
09:30 PM
@Hari Thapliyal Can you open a new thread and tag this one dates on 27, 2017
... View more
01-14-2019
03:37 PM
@Ahra Ko There is a step you missed, you should run the below,please adjust the HDF version to match ambari-server install-mpack --mpack=/tmp/hdf-ambari-mpack-3.3.0.0-165.tar.gz --purge --verbose After the restart of Ambari the Nifi service should be available HTH
... View more
01-14-2019
12:20 AM
@Marie-Christine GONTIER No of mappers depends on input split size it cannot be manually configured. Input split is a logical representation of data and block is a physical representation of data. An input split indicates the start and end point of data in a block. There is one mapper per input split. so the number of mappers is not completely dependent on the number blocks. Depending upon the configured size, the number of splits varies. There might be one split per block, one split per two blocks or maybe two splits per block and so on. HTH
... View more
01-14-2019
12:02 AM
@Adam J Nifi is not capable of spinning up a new node if one goes down,autoscaling is possible in AWS . AWS Auto Scaling monitors your applications and automatically adjusts capacity to maintain a steady, predictable predefined number of a node if a specifically configured alert is triggered eg Bad health or lost heartbeat. Kubernetes is another tool that you can use for auto-scaling best if your nifi is containerized HTH
... View more
01-13-2019
11:55 PM
@Divya Thaore You are trying to access the sandbox:8080 from your laptop because localhost:8080 translates to your local windows machine. To be able to access sandbox ambari from your Windows machine, you should have an entry in your hosts file in C:\Windows\System32\drivers\etc with the format IP:FQDN:ALIAS for example # localhost name resolution is handled within DNS itself.
#127.0.0.1 localhost
#::1 localhost
127.0.0.1 sandbox.hortonworks.com sandbox With the above entry assuming you sandbox IP is correctly you can access your cluster through http://sandbox:8080 HTH
... View more