Hi All,   we need to increase open file limit for nifi as a service not user , so add the below line in your nifi.service file and restart the server , it should resolve this issue   LimitNOFILE=999999 ... View more

Hello @yagoaparecidoti    Thanks for using Cloudera Community. Based on the Post, You encountered "Master Is Initializing" & ended up fixing the same using Command found on Internet. You ended up with few Tables in Broken State, requiring you to delete & recreate them.   For documenting the Post, the Issue observed is tracked via [1]. In the HMaster Logs, We should see HBase:Meta & HBase:Namespace Region, which aren't being assigned. Sample tracing shared via [1]. Once the same happens, Using HBCK2 Jar to assign the Region being reported as Unassigned is required. The Command to be used via HBCK2 Jar to assign the Region is shared via [1] as well.    The HBCK2 Command has other Options, which (If performed without any oversight) may cause issues with HBase Table availability. The "Master Is Initializing" Error Fix as shared via [1] shouldn't cause any Table to be in Broken State & without knowing the explicit details into the Broken State, It's harder to confirm if Delete-Recreate was the ONLY Way Or, We could have restored the Table in other ways.   Having said that, the Post covers "Master Is Initializing" Error & the same has been addressed. As such, We shall mark the Post as Closed. Feel free to share your observation with the Tables in Broken State in a New Post, if you wish to engage for the Community observation & feedback.    Regards, Smarak   [1] https://github.com/apache/hbase-operator-tools/tree/master/hbase-hbck2#master-startup-cannot-progress-in-holding-pattern-until-region-onlined   ... View more

Greetings @yagoaparecidoti    Thanks for using Cloudera Community. Based on the Post, you wish to confirm if the  "maxClientCnxns" Parameter set via CDM (Assuming you mean CM) for ZooKeeper Service is referred in any file associated.    You may refer to the Value of "maxClientCnxns" in "zoo.cfg" file associated with the ZooKeeper Process. In CDP/CDH (Managed by CM), You may refer to the same within the ZooKeeper Process Directory under "/var/run/cloudera-scm-agent/process/<ZooKeeper-Process-Directory>/zoo.cfg". The concerned file would be referred in the "ps" Output of the ZooKeeper Process as well.    Regards, Smarak ... View more

Thanks, everyone, for the help. ... View more

Greetings @melmoumni    Thanks for using Cloudera Community. For now, No to HA for Catalogd. This is coming from the fact stated in [1], wherein the Catalogd Unavailability don't leads to DataLoss & they can be removed to be added on a New Host without any impact. Similarly, the Upstream JIRA [2] remains Unresolved.    Again, I shall keep the Post available for others to provide their feedback, if they have tested the same. In [2], One User share their experience, which doesn't appear to be Successful.    Regards, Smarak   [1] https://impala.apache.org/docs/build/html/topics/impala_proxy.html [2] https://issues.apache.org/jira/browse/IMPALA-2702   ... View more

Hello @OmarElSeihy    Thanks for using Cloudera Community. Based on the Post, your Team is receiving a Warning [1]. By default, the Role uses "/tmp" for -XX:HeapDumpPath. Your Team need to change the Value set for -XX:HeapDumpPath to a Mount, wherein your Team have Sufficient Space. Alternatively, Your Team can work on reducing the FileSystem Usage on the concerned Mount Point.  This Warning is an Alert for Cluster Admin & has no impact on any Service Usage in the Cluster.  Sharing a Screenshot showing the Config Changes required, if your Team wish to modify the HeapDump Path & the Warning Threshold (Example shown for Solr Service as used Solr in the Post Tags):   Regards, Smarak   [1]  This role's Heap Dump Directory is on a filesystem with less than 10.0 GiB of its space free. /tmp ... View more

Hello @ganeshkumarj    Thanks for using Cloudera Community. Based on the Post, You are migrating from Cloudera Search (CDH 5.9.3) to Standalone Solr (Apache v4.10.3). As your Team mentioned, the Error points to Index (Copied manually) being on a Lucene Version higher than anticipated [1].    Your Team can confirm the LuceneVersion via "solrconfig.xml" for the Collection " sample_collection" on CDH. If LuceneVersion Match isn't feasible, ReIndexing is the Only Way forward. Yet, there are few things wherein our help in this Post would be limited: (I) CDH v5.9.3 is EoS since a long time. Internally, We have extremely limited Setup for checking further on your Team's concerns.  (II) Your Team is implementing the Migration on Standalone Solr (Apache v4.10.3). Cloudera Product Offering package Solr into Search (In CDH) & Solr (In CDP). Unfortunately, We have limited input on any Open Source Implementation outside of Cloudera Product.    Our Team would be happy to assist your Team to Migrate from CDH v5.9.3 to CDP, if required by your Team. We have Documentation (Which are Tested internally) to migrate from CDH Search to CDP Solr & your Team would get the Support assistance in any issues as well.    Regards, Smarak   [1] https://lucene.apache.org/core/7_1_0/core/org/apache/lucene/index/IndexFormatTooNewException.html   ... View more

It is already solved, it was only missing in the CREATE TABLE to add the sandbox path CLD_ML_BI_ENG.iris     dbExecute(conn = con_Hive, statement = "CREATE EXTERNAL TABLE CLD_ML_BI_ENG.iris(sepal_length double, sepal_width double, petal_length double, petal_width double, species varchar(10)) ROW FORMAT SERDE 'org.apache.hadoop.hive.ql.io.orc.OrcSerde' STORED AS INPUTFORMAT 'org.apache.hadoop.hive.ql.io.orc.OrcInputFormat' OUTPUTFORMAT 'org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat' LOCATION '/sandbox/CLD_ML_BI_ENG/iris'")   ... View more

Hello @rootuser,   Thanks for using Cloudera Community. Based on the Post, You are trying to use CopyTable to copy HBase Table(s) from 1 Cluster to another Cluster, wherein 1 Mapper is being observed.    Please confirm if the Source Table has 1 Region only. Additionally, Confirm if CopyTable on a Table with >1 Regions (Say, 5 Regions) creates 1 Mapper or 5 Mappers. Also, Please state the HBase Version being used by your Team. Additionally, Share the Timeout being observed by your Team.    As far as I recall, HBase uses 1 Mapper per Region. As such, It's likely the Source Table has 1 Region only. In such case, Increasing the Region Split by Pre-Split or Increasing the Timeout should help.    Regards, Smarak ... View more