@kellerj    You should use the following Kafka settings in this nifi processor:   1) Topic name  2) Broker name and it's port which you can check from the Kafka configuration  3) Kafka security protocol. You should check it from the Kafka side which protocol you are using whether it's SASL_PLAINTEXT or SASL_SSL 4) Keytab and principal which you want to use and having permission to produce data to Kafka topic  5) If you are using SASL_SSL protocol, then you will need to use Kafka SSL details.   Note 1: For the 4th and 5th number points you can add control services in your processors like KeytabCredentialsService & StandardRestrictedSSLContextService   Note 2: Keytab and SSL files (keystore & truststore) should be present on all nifi nodes and they should be accessible by the user. If ssl.client.auth=required is enabled in kafka >> conf, then you should use both keystore & truststore. If it's disabled, then use truststore only.   If you found this response assisted with your query, please take a moment to log in and click on  KUDOS 🙂 & ”Accept as Solution" below this post.   Thank you. ... View more

@Uday483    It looks like you have the case open for the same issue from the Cloudera ticket system and we are replicating and investigating this issue on priority.  We will share a workaround in the case and here in this community article as well so that it can help other users if they will come across the same issue.    Thank you.  ... View more

Hello @Uday483    Please let us know what type of rebalancing you are looking for when a broker comes online.    Is it disk / complete partitions rebalancing from other brokers to this broker (which comes online) OR only leader rebalance.    Thank you.  ... View more

Hello @Uday483    - You should check whether the CC endpoints are working as expected or not.  - Automatic rebalancing is DISABLED by default but it can be enabled by adding self.healing.enabled=true in cruisecontrol.properties advance snippet on CM UI. You can enable self-healing for specific types of events like broker failures, disk failures, metric anomalies or goal violations, etc.   More properties you can check at the below link.   https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/cctrl-overview/topics/cctrl-self-healing.html https://docs.cloudera.com/cdp-private-cloud-base/7.1.8/cctrl-configuration/cctrl-configuration.pdf   And below are the Rest-APIs you can use on CC without enabling self.healing as well. -- https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/cctrl-managing/topics/cctrl-using-rest-api.html --   If you found this response assisted with your query, please take a moment to log in and click on  KUDOS 🙂 & ”Accept as Solution" below this post.   Thank you. ... View more

@therealfortune    As per your OS version you can search it in google and build the OS base repo to install the necessary packages.  ... View more

  @therealfortune    After removing sandbox.repo please run the command "yum clean all" and initiate installation with the OS Base repos. Make sure that OS Base Repos are available/working using the default URLs.    If you are using CentOS6, then all the CentOS6 Base Repos are unavailable using the default URLs and you should replace OS Base repos with the vault one to resolve this issue.   Let us know if this information helped you.    ... View more

@mohammad_shamim    There is no other workaround for "HS2 role count in Hive and Hive on Tez services should match" other than making the role counts match. You need to add as many HS2 instances in HiveOnTez services as there are in Hive service prior the upgrade. The upgrade process requires this so that configuration from cdh HS2 instances can be mapped to cdp HS2 instances in a 1-to-1 fashion.   Can you please try adding Roles?   If you found this response assisted with your query, please take a moment to log in and click on  KUDOS 🙂 & ”Accept as Solution" below this post. ... View more

@skoch244    You should refer the following community article where we have explained updating/resetting offset possibilities for the topic in the Nifi processor.   https://community.cloudera.com/t5/Support-Questions/Offset-handling-in-Apache-NiFi-consumeKafka/m-p/303112/highlight/true#M221400   Please let us know if this information helped you.    Thank you. ... View more

@NishanthP   1) Cloudera does not have its own Kafka Web APIs. But obviously, we do not restrict to use of any other 3rd party connectors / APIs. You can use any third-party APIs and can easily integrate with Cloudera Kafka.    2) Second and the best alternative is that NiFi has its own native support for producing and consuming from Kafka, so you should not need to use the REST API.    3) Alternatively, SRM/SMM APIs can help here [1],[2]   [1] Under CDF, there is Cloudera Stream Processing (CSP) https://docs.cloudera.com/csp/2.0.1/index.html   [2] and under "SMM REST API Reference" there is a host of REST API. https://docs.cloudera.com/smm/2.0.0/rest-api-reference/index.html   If you found this response assisted with your query, please take a moment to log in and click on  KUDOS 🙂 & ”Accept as Solution" below this post.   Thank you. ... View more

@Sagar_cloudera    Looks like the host has network connectivity issues.   Please check if there are any network connectivity issues if not, then provide us the complete details/error you are getting while installing Cloudera so that we can suggest you on it further.    Thank you. ... View more