Member since
11-17-2021
1169
Posts
264
Kudos Received
30
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 545 | 04-23-2026 02:02 PM | |
| 1208 | 03-17-2026 05:26 PM | |
| 7085 | 11-05-2025 10:13 AM | |
| 1382 | 10-16-2025 02:45 PM | |
| 2253 | 10-06-2025 01:01 PM |
09-17-2026
11:33 AM
1 Kudo
Important Timeline Update: Read-Only Mode Started on September 21
Evolving the Cloudera Community
What to Expect in Our Upcoming Upgrade
The Cloudera Community runs on your expertise: the questions you ask, the solutions you share, and the knowledge you pass along to the next person stuck on the same problem. To give that collaboration a stronger foundation, we're upgrading to a new community platform.
This upgrade comes down to three things: helping you find answers faster, making it easier to share solutions, and giving you clearer recognition for what you contribute. Here's what's changing, when it's happening, and what to expect on the other side.
Important Timeline Update: Read-Only Mode Started on September 21
To safely carry every post, reply, and accepted solution into the new environment, the Community will enter a temporary read-only mode starting September 21.
What this means for you: You can still search, browse, and read every existing discussion and article.
What's paused: New forum posts, replies, and direct messages will be paused temporarily while we migrate the database.
The exception: All Blogs stay active, so new content keeps publishing without interruption.
Action requested before September 21st
If you currently have content saved as a draft in Cloudera Community, please review and clear your drafts before read-only mode begins. We recommend completing, publishing, or saving elsewhere any draft content you may need before September 21.
Taking this step before the transition will help ensure that any work currently in progress is addressed before publishing capabilities are temporarily limited.
A Sneak Peek at the Upgrades
We built this new space around how developers and technical practitioners actually work. Here's what changes on day one.
An Upgraded Code Editor
We know how much code gets shared here, so the new editor was designed around that. Expect built-in numbered lines for every snippet and a one-click “copy code” icon, no more manually selecting and copying.
Refreshed UI and Search
The homepage is getting a cleaner, more modern look, and navigation is far more streamlined. Search has also been upgraded, so you can cut through the noise and land on the specific technical answer you need, faster.
An Intuitive, Metal-Based Ranking System
We're overhauling our ranks to make community standing easy to read at a glance. The new system uses metal tiers (Bronze, Silver, Gold), with stars marking your depth within each tier, so “Gold :star: ” means level one of the Gold group. Your hard-earned reputation carries over automatically, and this new structure makes it easier to spot our top contributors.
What's Next?
Your history and your posts are safe. The read-only window is simply the mechanical step that carries your contributions into the new system intact.
This is just the high-level view. Stay tuned to the Community Blogs over the coming days for deeper dives into each of these features, plus a practical checklist to help you navigate the new space on launch day.
Thank you for building with us. We can't wait to show you the new Cloudera Community!
... View more
09-03-2026
10:43 AM
1 Kudo
Hello @Softwarebyt, Based on the error posted for @ipson, looks like this matches two NiFi Jiras: https://issues.apache.org/jira/browse/NIFI-13720 https://issues.apache.org/jira/browse/NIFI-13722 Those fixes get included on CFM 2.1.7.1000: https://docs.cloudera.com/cfm/2.1.7/release-notes/topics/cfm-fixed-issues.html And CDF for DataHub 7.3.1.0: https://docs.cloudera.com/cdf-datahub/7.3.1/release-notes/topics/cdf-datahub-fixed-issues-flow-management.html
... View more
08-24-2026
04:12 PM
@DevOpsWorld Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
08-07-2026
09:55 PM
1 Kudo
Here are some highlights from the month of June
Upcoming Events
Read Here
Watch Now
Community Authors Leaderboard
@MattWho @9een @upadhyayk04 @tnair @RAGHUY
... View more
07-24-2026
06:05 PM
@solardelune Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
07-01-2026
04:04 PM
1 Kudo
Here are some highlights from the month of May
Upcoming Events
Read Here
Register Here
Community Authors Leaderboard
@MattWho @RAGHUY @vafs @ganzuoni @AlokKumar
Community Unanswered Questions
... View more
06-30-2026
10:16 AM
Hello @moekraft, Thanks for reaching our community. As of now, none of the runtimes supports JDK 21. But I see there are efforts to include support for it on newer but also on those LTS releases. Still we do not have information to share about the estimated time, but you can be sure that Cloudera is actively checking on the supported depencies and their EOS to always have a supported version. You should expect that in the future, before the EOS is met, Cloudera would provide support and communications.
... View more
06-25-2026
03:08 AM
Spark lazily evaluates the workload. The actual execution happens when you write the output, usually. If it gets stuck there that means the workload is not tuned with respect to your infrastructure. Try checking the logs, most likely you need to tune your shuffle partition and/or repartition your data.🙂
... View more
06-08-2026
12:27 AM
Thank you for the great insights These are the disctp options distcp -skipcrccheck -copybuffersize 32768 -update -pugp -bandwidth 50 -strategy dynamic and yes, total execution time increases almost linearly with nr of files/directories
... View more
06-02-2026
10:40 AM
1 Kudo
Cloudera Support helped me resolved this issue. * The "Bad Health" status displayed in Cloudera Manager was a false-positive monitoring alert. * The Cloudera Manager Service Monitor (SMON) was failing its secure TLS connection handshakes to ZooKeeper due to strict endpoint identification checks introduced in modern Java runtimes (Java 17). Because SMON couldn't pull health metrics, it flagged ZooKeeper as down. * The solution is to configure the JVM argument inside the SMON configuration "Java Configuration Options for Service Monitor (firehose_java_opts)" to bypass the strict certificate hostname checks: `-Djdk.rmi.ssl.client.enableEndpointIdentification=false`. This cluster is 7.1.9sp1 with 7.13.1 CM. Strangely, another cluster, which has the same cluster version, CM version, and Java version, had no such issue. It was set up six months ago. Thanks for all the responses. Best regards,
... View more