How to update custom stack version number in ambari
Here is the example to update this in the UI for a Mahout service. You can do the same for your custom service like HAProxy.
Take backup:-
create table repo_version_bkp as select * from repo_version;
Query to check the data before update:-
select replace(version_xml,'name="MAHOUT" version="0.9.0"','name="MAHOUT" version="0.9.1"') from repo_version where repo_version=1;
Check the output of this select sql, it should show what the replaced value is. Here i am replacing the string (name="MAHOUT" version="0.9.0"') from the column version_xml and the replaced value will be (name="MAHOUT" version="0.9.1").
Update:
Once you confirm the output looks correct, then update the table.
update repo_version set version_xml=replace(version_xml,'name="MAHOUT" version="0.9.0"','name="MAHOUT" version="0.9.1"') where repo_version_id=1;
Note: use the correct repo_version_id number in the above query based on your environment.
After the table change restart Ambari-server
Installing CDSW on HDP Cluster
Cluster Requirement:-
- Enable memory cgroups on your operating system (Use RHEL7.5 - and should be enabled by default)
- Disable swap for optimum stability and performance.
- Cloudera Data Science Workbench uses uid 8536 for an internal service account. Make sure that this user ID is not assigned to any other service or user account.
- JDK 8
- Disable all pre-existing iptables rules.
sudo iptables -P FORWARD ACCEPT
sudo iptables -P OUTPUT ACCEPT
sudo iptables -t nat -F
sudo iptables -t mangle -F
sudo iptables -F
sudo iptables -X
- Disable SELINUX or permissive mode.
- No DNS server running on port 53 the CDSW machines ( check by running lsof -i:53)
- yum -y install bzip2
- Install anaconda
- /anaconda/anaconda2
- Read and agree and type "yes"
Install CDSW:
- Add a new host to the cluster using ambari. Go to the Hosts page and select Actions > + Add New Hosts.
- On the edge node,
- sudo yum install cloudera-data-science-workbench
- vi /etc/cdsw/config/cdsw.conf
- cdsw init
Reference:
How to rename a existing HDP cluster
How to Fix Ranger Usersync Failure on Your HDP / CDP Cluster
If you're setting up a cluster and experiencing issues with Ranger usersync, you may encounter error messages in the /var/log/ranger/usersync/usersync.log file. Specifically, you might see errors like the following:
11 Feb 2022 15:15:46 ERROR CustomSSLSocketFactory [UnixUserSyncThread] - Unable to obtain keystore from file [/usr/hdp/current/ranger-usersync/conf/mytruststore.jks]
11 Feb 2022 15:15:46 ERROR UserGroupSync [UnixUserSyncThread] - Failed to initialize UserGroup source/sink. Will retry after 3600000 milliseconds. Error details: javax.naming.CommunicationException: adhost1.example.com:636 [Root exception is java.lang.NullPointerException]
These errors can be frustrating to deal with, but there are steps you can take to address them. One solution involves extracting an Active Directory (AD) cert and importing it into the Ranger usersync truststore. Finally, you'll need to update the password for the truststore through Ambari. By following these steps, you can get Ranger usersync up and running smoothly.
Solution: How to Fix Ranger Usersync Failure on Your Cluster
To resolve this issue, follow these simple steps:
Step 1: Extract the AD cert To extract the AD cert, use the following command:
perlecho -n | openssl s_client -connect adhost1.example.com:636 \ | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > /tmp/ad_cert.cert
Step 2: Import the extracted cert into Ranger usersync truststore To import the extracted cert into the Ranger usersync truststore, use the following command:
bashkeytool -import -trustcacerts -alias AD_cert -keystore /usr/hdp/current/ranger-usersync/conf/mytruststore.jks -file /tmp/ad_cert.cert
Make sure to choose the password you want to set for this keystore.
Step 3: Update the Ranger usersync truststore password To update the password for the Ranger usersync truststore, follow these steps:
- Go to Ambari.
- Navigate to Ranger --> Configs --> Advanced --> Advanced ranger-ugsync-site --> ranger.usersync.truststore.password.
- Update the password.
By following these simple steps, you should be able to fix the Ranger usersync failure on your cluster.
How to install localstack - to use S3 API's onprem cluster
curl -sL https://rpm.nodesource.com/setup_10.x | bash -
yum -y install python-pip python-devel gcc gcc+ nodejs maven lsof wget
pip install --upgrade pip
pip install localstack awscli-local
Ambari - How to store KDC admin credential persisted and regenerate keytabs using API call
Step1:
ambari-server setup-security
and choose [2] Encrypt passwords stored in ambari.properties file
and choose the password you want to set
OS commands
Boost Your Download Speed with lftp Segmentation
Looking for a faster way to download files via sftp to a Linux machine? Try using "lftp" instead. This tool offers segmented downl...
Other relevant topics
-
Hive metastore DB Connection verification from Command line:- You can run the following on any node where ambari agent installed on the ...
-
Using PIG to load into Hbase:- In this article we will see how to join 2 datasets in PIG and load the joined, filtered data into HBASE t...
-
+++++++++++++++++++++++++++++++++++++++++++ How to move a region from 1 RS to another Region server:- ++++++++++++++++++++++++++++++++++++...