Member since
01-19-2017
3679
Posts
632
Kudos Received
372
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 945 | 06-04-2025 11:36 PM | |
| 1552 | 03-23-2025 05:23 AM | |
| 772 | 03-17-2025 10:18 AM | |
| 2783 | 03-05-2025 01:34 PM | |
| 1833 | 03-03-2025 01:09 PM |
02-11-2019
03:26 PM
@Sampath Kumar If you are interested to resolve the issue then try out match the encryption types and tag me if need be?
... View more
02-11-2019
02:05 PM
@Daniel Nguyen I hope you replaced the "my_host_name.com" with the output of $ hostname -f Meaning the FQDN of the nifi host just to be sure we have the same understanding?
... View more
02-11-2019
10:07 AM
@heta desai How do I manage and configure block/chunk size and the replication factor with WASB? You don't. It's not generally necessary. The data is stored in the Azure storage accounts, remaining accessible to many applications at once. Each blob (file) is replicated 3x within the data center. If you choose to use geo-replication on your account you also get 3 copies of the data in another data center within the same region. The data is chunked and distributed to nodes when a job is run. If you need to change the chunk size for memory-related performance at run time that is still an option. You can pass in any Hadoop configuration parameter setting when you create the cluster or you can use the SET command for a given job. Reference: Understanding WASB and Hadoop Storage in Azure
... View more
02-11-2019
07:45 AM
@heta desai The simple answer is YES The hadoop-azure file system layer simulates HDFS folders on top of Azure storage. Windows Azure Storage Blob (WASB) is an extension built on top of the HDFS APIs.It in many ways "is" HDFS. However, WASB creates a layer of abstraction that enables the separation of storage. This separation is what enables your data to persist even when no clusters currently exist and enables multiple clusters plus other applications to access a single piece of data all at the same time. This increases functionality and flexibility while reducing costs and reducing the time from question to insight. HDInsights which is a Hortontworkd offering in Azure runs against WASB Azure doesn't have the notion of a directory. However, the parsing of the file name gives the tree structure because Hadoop recognizes that a slash “/” is an indication of a directory. Blob address: # Fully Qualified name Local hdfs://<namenodehost>/<path> # HDInsight Syntax Global wasb[s]://<containername>@<accountname>.blob.core.windows.net/<path> # Example wasb://YOURDefaultContainer@YOURStorageAccount.blob.core.windows.net/SomeDirectory/ASubDirectory/AFile.txt Hope that enlightens your knowledge
... View more
02-11-2019
07:03 AM
@Sampath Kumar So you have disabled Kerberos for HTTP web-consoles was that intentional on a kerberized cluster or just a workaround?
... View more
02-10-2019
10:43 PM
@Dukool SHarma Any updates?
... View more
02-10-2019
10:37 PM
@Sampath Kumar Any updates did this article help you ?
... View more
02-10-2019
10:14 PM
1 Kudo
@Michael Bronson HWX doesn't recommend upgrading an individual HDP component because one never knows the incompatibilities that could impact the other components and component selective upgrades tend to be a nightmare during a version upgrade The lastest HDP Kafka version is 11-2.1.x delivered by HDP 3.1 but ASF has its own rollout version and naming convention HTH
... View more
02-10-2019
09:31 PM
1 Kudo
@Manjunath P N The latest HDP 3.1, unfortunately, supports spark 2.3, so you will have to wait for the next major release but after the Cloudera & Hortonworks merger, my best guess is don't expect any new HDP version anytime before the release of the combined new offering Cloudera Data Platform (CDP) sometime in 2020 or thereafter. I would imagine currently HWX and CLDR should be more focused on the integration of the new products than really trying to release a newer version. The new combined offering CDP will be based on HDP 3.x and CDH 5 HTH
... View more