About upadhyayk04

upadhyayk04 · ‎07-09-2024

Hello @naju This is an OS repo error. The 404 indicates that the repository locations that you have in repo files which are located in /etc/yum.repos.d/ have incorrect URLs Either fix those URLs manually and run the following command # yum clean all # rm -rf /var/cache/yum # yum repolist or else you might need to check with your OS team

upadhyayk04 · ‎06-17-2024

Hello @OlivierT Thank you for reaching out Can you please share the output of the below to see what is creating this process? # ps -ef | grep -i 25833

upadhyayk04 · ‎06-17-2024

Hello @rahuledavalath Yes only the incremental data will be copied Yes bi-direction will only work if you set the replication policy on both the source and target

upadhyayk04 · ‎06-07-2024

Hello @rahuledavalath In this case, you must create a replication policy on both the source and target. Also, Incremental data from BDR will be copied back to prod once your actual prod is up again

upadhyayk04 · ‎06-03-2024

Hello @soumM Yes that is pretty strange, I don't how you have configured this What version of CM CDP are you using? Check CM UI >> Cloudera Management Services >> Configuration >> Roll Group and check what do you see there?

upadhyayk04 · ‎05-27-2024

Hello, Thank you for reaching out The override is there so that if you have a role running on 2-3 nodes and you want to override a configuration on a particular host you can do that. If you want same for all nodes then you can set that up in Default group

upadhyayk04 · ‎05-21-2024

Hello @npdell Thank you for reaching out. May you refer already answered discussion below https://community.cloudera.com/t5/Support-Questions/Grafana-support-in-CDP-data/td-p/356499 The above will help you to proceed further

upadhyayk04 · ‎05-09-2024

Hello @soumM Thank you for reaching out Do you see GC paused in SMON logs? Can you try increasing the java heap size to 4GB Regarding the connection timeout messages try performing a telnet from SMON host to the host on which you are observing in the logs (hostname and port) # telnet <target-hostname> <port>

upadhyayk04 · ‎04-25-2024

Hello, Thank you for your update Do you need a proxy for yum to reach out to that IP Check if proxy is present as environment variable as well # env | grep -i proxy

upadhyayk04 · ‎04-24-2024

Hello, Thank you for your update I could see enabled field is missing in Cloudera Manager repository Can you please check the output of following command and see if packages are installed the yum is working fine # rpm -qa | grep -i cloudera # rpm -qa | grep -i jdk # yum clean all # yum repolist

Online	Online
Last Visited	‎10-09-2025 01:17 PM

Member Since	‎02-07-2022 04:14 AM
Last Visited	‎10-09-2025 01:17 PM
Posts	252
Kudos received	60

Cloudera Community

Re: Apache Ozone -1.4. Upgrading parcel version t...

Re: swap warning

Re: Getting access denied in MariaDB for Reports M...

Re: Import of cloudera tempalte failed

Re: Deployment and configuration steps with CM Res...

Re: I'm not able to install pip in HDP 2.6.5 from ...

Re: Agent Heartbeat problems on datanodes

Re: In CDP Private Cloud Base, will the Replicatio...

Re: In CDP Private Cloud Base, will the Replicatio...

Re: Service Monitor Heap size issue

Re: Service Monitor Heap size issue

Re: Is it possible to store the CM timeseries char...

Re: Service Monitor Heap size issue

Re: CDP Cloudera Manager Fails to install Cloudera...

Re: CDP Cloudera Manager Fails to install Cloudera...