Member since
10-04-2017
113
Posts
11
Kudos Received
9
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
18164 | 07-03-2019 08:34 AM | |
2081 | 10-31-2018 02:16 AM | |
12788 | 05-11-2018 01:31 AM | |
8414 | 02-21-2018 03:25 AM | |
2917 | 02-21-2018 01:18 AM |
06-29-2021
04:40 AM
I have upgraded from 7.1.1 to 7.1.6 and "Upgrade Ranger database and apply patches" is grayed out.
... View more
05-29-2020
07:14 AM
I did follow the similar steps but had the issue. I had to remove all the KTS/KMS installation start from scratch which fixed the issue but this time i added only one server first and then added the other.
... View more
04-16-2020
07:48 AM
I am enabling HDFS data at rest encryption in CDH 6.3 and while adding the KMS service, i noticed that /var/lib/kms-keytrustee/keytrustee/.keytrustee/ is actually doesn't exist on all the KMS hosts when trying to synchronise the KMS hosts private keys. Has anyone come across such issue and what is the way forward for this?
... View more
Labels:
12-17-2019
01:33 AM
@pdev have you disabled TLS in the management services as well? After you disable/enable TLS, you will have restart the management services so they communicate with CM with the changed port and protocol.
... View more
07-03-2019
08:34 AM
2 Kudos
@satz We were able to resolve this. We had the kerberos auth principles in default kafka group while all the broker were in a different config group. Adding the auth principles to the kafka config group has solved the issue.
... View more
06-09-2019
12:36 AM
Hi, We have just built a new kafka cluster(3.1.0-1.3.1.0.p0.35) and integrated it with kerberos. Kerberos is integrated with AD. We are able to produce and consume with kafka principle which is local but with AD users, it fails with below error on console. 19/06/09 08:14:22 DEBUG authenticator.SaslClientAuthenticator: Set SASL client state to CLIENT_COMPLETE 19/06/09 08:14:22 DEBUG authenticator.SaslClientAuthenticator: Set SASL client state to COMPLETE 19/06/09 08:14:22 DEBUG clients.NetworkClient: [Producer clientId=console-producer] Initiating API versions fetch from node -1. 19/06/09 08:14:22 DEBUG network.Selector: [Producer clientId=console-producer] Connection with server2.kafka4.corp/180.20.92.23 disconnected java.io.EOFException at org.apache.kafka.common.network.NetworkReceive.readFromReadableChannel(NetworkReceive.java:124) at org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:93) at org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:235) at org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:196) at org.apache.kafka.common.network.Selector.attemptRead(Selector.java:545) at org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:483) at org.apache.kafka.common.network.Selector.poll(Selector.java:412) at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:481) at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:239) at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:163) at java.lang.Thread.run(Thread.java:748) 19/06/09 08:14:22 DEBUG clients.NetworkClient: [Producer clientId=console-producer] Node -1 disconnected. 19/06/09 08:14:22 INFO clients.NetworkClient: [Producer clientId=console-producer] API versions request failed via disconnect. Defaulting legacy API versions 19/06/09 08:14:22 DEBUG clients.NetworkClient: [Producer clientId=console-producer] Give up sending metadata request since no node is available 19/06/09 08:14:22 DEBUG clients.NetworkClient: [Producer clientId=console-producer] Give up sending metadata request since no node is available ^C19/06/09 08:14:22 INFO producer.KafkaProducer: [Producer clientId=console-producer] Closing the Kafka producer with timeoutMillis = 9223372036854775807 ms. 19/06/09 08:14:22 DEBUG internals.Sender: [Producer clientId=console-producer] Beginning shutdown of Kafka producer I/O thread, sending remaining records. ========================================== The broker logs only have errors about the shortname for users. Caused by: org.apache.kafka.common.security.kerberos.NoMatchingRule: No rules apply to RAJESH@KAFKA4.CORP, rules [DEFAULT]
... View more
Labels:
- Labels:
-
Apache Kafka
-
Kerberos
05-29-2019
05:42 AM
If you install cloudera manager packages and start the agent, it will not distribute the parcels. The parcels will be distributed only when you add the host to the cluster.
... View more
05-29-2019
05:27 AM
Clouder amanager would automatically distribute the parcels that the cluster requires.
... View more
05-29-2019
04:31 AM
@Fawze You can mention multiple parcel links in cloudera manager so it should not be an issue.
... View more
11-28-2018
02:35 AM
Hi @manuroman I have read the page but couldn't validate myself on how many nodes are actually under billing. The License page in CM shows below and makes sense as we have 10 gateways and they are excluded in the total below. Is the billing calculated based on how many nodes have the core product or based on how many nodes are under navogator? Total Nodes : 101
... View more