1 | [root@hdf-server01 ambari-server]# ambari-server setup-ldap |
After setup , run below command to trigger the sync.
1 | ambari restart |
1 | [root@hdf-server01 ambari-server]# ambari-server setup-ldap |
After setup , run below command to trigger the sync.
1 | ambari restart |
1 | [root@hdf-server01 ambari-server]# ambari-server setup-ldap |
After setup , run below command to trigger the sync.
1 | ambari restart |
1 | vi /var/lib/pgsql/data/pg_hba.conf |
add below line to give access,
1 | local all angerdba trust |
1 | psql rangerdb -U rangerdba |
1 | update x_portal_user set password = 'ceb4f32325eda6142bd65215f4c0f371' where login_id = 'admin'; |
https://cwiki.apache.org/confluence/display/KAFKA/Transactional+Messaging+in+Kafka
https://medium.com/@andrew_schofield/does-apache-kafka-do-acid-transactions-647b207f3d0e
So, does Apache Kafka do ACID transactions? Absolutely not. No way. Can you get a similar effect? If you design your applications in the right way, yes. Does it matter? In many cases, not really, but when it does, you absolutely don’t want to get it wrong. Just take the time to understand the guarantees that you need to make your system reliable and choose accordingly.
DB->Topic xa transaction, can do
Topic->DB xa transaction, hard to implmement
The JMX for kafka is by default turned on by Ambari
From local machine, switch to the JDK folder and run jconsole
1 | <JDK_Home>/bin/jconsole |
With the UI, use kafkaBrokerhostName:16667 as the connection string to connect to Kafka.
1 | mkdir -p /opt/kafka-tools |
For Ambari managed Kafka, configure autostart from Console
http://[ambari-host]:8080/#/main/admin/serviceAutoStart
By default, the Kafka and zookeeper “autostart” function provided by Ambari is stopped. For any env other than DEV this is be modified to enabled.
To change kakfa configuration,
Kafka SASL relying on Kerberized cluster.
Configuration Name | Value |
---|---|
KDC Type | Existing Active Directory |
KDC hosts | kdcserver1,kdcserver2 |
Realm name | DOMAINNAME.CAPITAL.NET |
LDAP url | ldaps://ldapserver1.domainname.capital.net:636 |
Container DN | OU=AmbariCluster, DC=net |
Domains | DOMAINNAME |
Kadmin host | kdcserver1 |
Admin principal | SUPERUSER |
Admin password | password |
make sure the kerberos-provider details is defined at “Template for login-identity-providers.xml”.
1 | <provider> |
After kerbereros is enabled, the ldap user name logged in may contains domain like username@domain.com
1 | [root@hdf-server01 ambari-server]# ambari-server setup-ldap |
After setup , run below command to trigger the sync.
1 | ambari restart |