Member since
09-29-2015
5226
Posts
22
Kudos Received
34
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1391 | 07-13-2022 07:05 AM | |
3584 | 08-11-2021 05:29 AM | |
2326 | 07-07-2021 01:04 AM | |
1572 | 07-06-2021 03:24 AM | |
3540 | 06-07-2021 11:12 PM |
06-11-2020
02:19 AM
Hello @Fawze , thank you for raising your question regarding on our Common Vulnerabilities and Exposures (CVE) processes. Please see [1] and [2] articles on how we handle vulnerabilities and [3] for the Security Bulletins. Q1) Is the patching process part of the CDH versions, if i need to apply a patch do i have other ways without upgrading the CDH version? A1) for Cloudera Customers there is a patching process available, however the process is equivalent to deploying to a new minor version. Therefore we encourage applying the latest minor versions instead of patching when fix is available. There are situations when patching is not possible because of the amount of code change / redesign required. If you are a subscription customer, please file a Support ticket on our Support Portal listing all your requirements and we will guide you through the process. When you are in the process of redesigning your cluster, please involve your Account Team (Sales Team) as early as possible, as they might able to assist you to build a more robust system. Q2) Is there a dedicated board for cloudera/hadoop vulnerability issues that can be used as source of truth? A2) Yes, it is called Security Bulletins. Please see [3] Q3) Where i can get the patches? is it requesting subscription? A3) Yes, it is required to have a subscription to access Support. We understand that patching is an expensive exercise, therefore we do our best to identify options on how to resolve your issue, which might not require a patch. Please always apply the latest minor version release for your Cloudera software, as it contains the latest bug fixes. By this you can reduce the likelihood of downtime. Q4) For example, i want to follow this one https://nvd.nist.gov/vuln/detail/CVE-2019-14449 , is it mean to get this done i need to upgrade to 5.16.2 or there is a patch that i can download and run it? A4) Based on [3] there is no workaround identified, which means you have to upgrade to a version that contains the fix: Cloudera Manager 5.16.2, 6.0.2, 6.1.1, 6.2.0, 6.3.0 Since the issue affects CM only, you do not need to upgrade your CDH, only CM. Please let us know if we answered all of your enquiries and if so, please mark the answer as the solution, so it will be easier for other community members to find it. Best regards: Ferenc [1] http://blog.cloudera.com/blog/2016/05/clouderas-process-for-handling-security-vulnerabilities/ [2] http://www.apache.org/security/committers.html#vulnerability-handling [3] https://docs.cloudera.com/documentation/other/security-bulletins/topics/Security-Bulletin.html
... View more
06-08-2020
01:07 AM
Hello @Mondi , thank you for raising your question about why application logs being deleted from the nodes after the applications finished running and why is it happening, how to keep them in place. When log aggregation is enabled with the 'yarn.log-aggregation-enable = true' [1] you will observe the behaviour described: after the logs are aggregated to HDFS, the logs are immediately deleted from the local file system. Log aggregation does not start until the application is finished. If you need to keep the logs and some other temporary files on the local node for troubleshooting and you have log aggregation turned on then you can use yarn.nodemanager.delete.debug-delay-sec . This is set to 0 seconds by default causing the immediate delete. Should you disable log aggregation, non aggregated logs are kept for yarn.nodemanager.log.retain-seconds = 10800 seconds (3*3600 seconds or 3 hours). After that the NodeManager will delete the log files. Please let us know if your enquiries been addressed! Thank you: Ferenc [1] https://hadoop.apache.org/docs/r2.7.0/hadoop-yarn/hadoop-yarn-common/yarn-default.xml
... View more
06-05-2020
06:58 AM
@Mondi You would still need to secure your cluster since any user can be impersonated in a non kerberised cluster. Refer https://blog.cloudera.com/how-to-secure-internet-exposed-apache-hadoop/ for more details on securing your cluster.
... View more
06-02-2020
07:33 AM
Thanks Ferenc. As mentioned, we cannot use CDP in the foreseeable future, nor are we customizing the CDH release in any real way -- simply adding Livy on a new edge node, which should work and should be relatively straightforward, but in this case is not. Enterprise Support (which we pay for) is telling us to ask the Community for guidance. So, here we are. If anyone has any guidance in terms of actually getting past this local auth mapping issue, we would greatly appreciate it. Best, Mike
... View more
05-30-2020
07:08 PM
1 Kudo
Hello, @Bender Yes, I have got the link [2] from your reply Thank you very much! Paul
... View more
05-14-2020
09:54 PM
Hi @StevenOD , I have run the command wget , but I didn't download the cloudera-manager-installer-bin, I just save to file name : 915156417?h=6ctV9nXcIRIHhcRwXIpyDmo7gw2u2mfCRaNSW_srWgc The output messages like these : --2020-05-14 18:29:18-- https://www3.cloudera.com/e/593381/cloudera-manager-installer-bin/2cyngcx/915156417?h=6ctV9nXcIRIHhcRwXIpyDmo7gw2u2mfCRaNSW_srWgc Resolving www3.cloudera.com (www3.cloudera.com)... 52.202.69.186 Connecting to www3.cloudera.com (www3.cloudera.com)|52.202.69.186|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://archive.cloudera.com/cm7/7.0.3/cloudera-manager-installer.bin [following] --2020-05-14 18:29:26-- https://archive.cloudera.com/cm7/7.0.3/cloudera-manager-installer.bin Resolving archive.cloudera.com (archive.cloudera.com)... 151.101.8.167 Connecting to archive.cloudera.com (archive.cloudera.com)|151.101.8.167|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 830137 (811K) [application/octet-stream] Saving to: ‘915156417?h=6ctV9nXcIRIHhcRwXIpyDmo7gw2u2mfCRaNSW_srWgc’ 100%[==================================================================>] 830,137 --.-K/s in 0.1s 2020-05-14 18:29:27 (6.08 MB/s) - ‘915156417?h=6ctV9nXcIRIHhcRwXIpyDmo7gw2u2mfCRaNSW_srWgc’ saved [830137/830137] Regard, BSST
... View more
05-13-2020
01:55 AM
1 Kudo
Hello @BSST , this page details about memory and storage recommendations per host: https://docs.cloudera.com/cdpdc/7.0/release-guide/topics/cdpdc-hardware-requirements.html Is it what you were looking for, please? Thank you: Ferenc
... View more
05-06-2020
07:57 AM
1 Kudo
Hello @matagyula , thank you for your feedback on the proposed actions and for accepting the reply as the solution! It will help Community Members facing with similar issues to find the answer faster. Üdvözlettel: Ferenc
... View more
05-04-2020
02:27 AM
Hello @Sergiete , thank you for raising our attention that there was an improvement point in Cloudera CDP documentation. We have added clarification in our CDP documentation about "Installing Hive on Tez" [1] and that the Spark execution engine is not supported, as it's been replaced by Tez [2]. Based on our updated documentation [1] the correct order of installing the Hive service is: Install the Hive service, designated Hive on Tez in CDP. HiveServer is installed automatically during this process. Install HMS, which is designated Hive. Best regards: Ferenc [1] https://docs.cloudera.com/runtime/7.0.3/hive-introduction/topics/hive_installing_on_tez.html [2] https://docs.cloudera.com/runtime/7.0.3/hive-introduction/topics/hive-unsupported.html
... View more
04-22-2020
08:34 AM
Yup working now 🙂 Now i am stuck up in PutMongo to update the existing document in collection. Please see my question and help me . need a push here 🙂
... View more
- « Previous
- Next »