Hello @qu1etstorm    The Logs  FileNotFoundException & YouAreDeadException are typically observed after the Cause, so worth checking the Logs before the concerned 2 Exception. TheYouAreDeadException is thrown by the Master when a RegionServer reports and is already being processed as Dead. This can happen when aRegionServer loses its session but didn't figure it yet. So, Best to check with respect to the RegionServer ZNode Session tracking in the Logs, while comparing the time at when the Master detected the RegionServer Ephemeral ZNode as being removed. Typically, JVMPause are the most likely cause.    - Smarak ... View more

Hello @amit_    The Post is couple of months old, yet wish to know if you have fixed the issue. The Lease seems to have expired after ~30 Minutes as per your Configuration. However, the Log shows a processingTime of ~30/~60 Seconds for ~5MB of Scan Size, so the Scanner Lease expiring after ~30 Minutes looks strange & appears to be caused by either the Client going away somehow or the processingTime being excessively slow.    If you have fixed the issue, Will appreciate your feedback on the Post.   - Smarak  ... View more

Thank You @Seaport for sharing the Solution for wider audience. In short, you followed the Link [1] to resolve the Protocol Header Issue as utilised by the User in Link [2].    - Smarak   [1] https://github.com/python-happybase/happybase/issues/161 [2] https://community.cloudera.com/t5/Support-Questions/Sharing-how-to-solve-HUE-and-HBase-connect-problem-on-CDH-6/td-p/82030   ... View more

Hello @jiaozz    It's an Old Post, yet submitting a response to anyone encountering such issue. Yet, Kindly test the 2 approaches below: (I) At Hive Session Level, Execute " ADD   FILE  <HBase Configuration File> " (II) Add the HBase Config to "HIVE_AUX_JARS_PATH" Path at Hive Service Level.    In short, the issue appears upon HBase Config being not correctly set, even though the 1st Create Table Hive SQL runs successfully yet fails upon any Table created referencing the Hive Table created in the 1st SQL.    - Smarak ... View more

Hello @ASIF123    Atlas Janus is an HBase Table, created with Column Family specification only. The DDL of the concerned Atlas Table is available in the HMaster UI & Master Logs, when Atlas Service is initialised for 1st time. However, Column Families are added eventually & each Row of the concerned Table has Different Column Qualifier. In short, there is no Static Definition of Atlas Janus Table.    Any Phoenix Table or View mapping requires explicit specification of the Column Family & Column Qualifier. Henceforth, the Phoenix Table or View DDL will be specific to Customer's Env. Your team can review the Atlas Janus Table Output via Scan & confirm the Column Qualifier against each Column Family. Accordingly, the Phoenix Table or View can be created.    - Smarak ... View more

Hello @rameshlk    Maybe this Post by Josh Elser would help, wherein he discussed using PQS behind Load Balancer to achieve High Availability: https://community.cloudera.com/t5/Community-Articles/Deploying-the-Phoenix-Query-Server-in-production/tac-p/245110   - Smarak ... View more

Hello @kras    I was able to reproduce the concerned behaviour as well. Checking internally on the Steps to safely remove the Secondary Regions. Shall Update the Post once a Solution is found.   - Smarak ... View more

Hello @Manoj690    The best way would be to check the RegionServer Logs wherein the Region are stuck in OPENING State. The fact that Count of Region-In-Transition is reducing with time & Increasing again upon HBase Service Restart indicates the Regions are likely waiting on WAL Split & Edit Replay. With 3 RegionServer, 7K RIT indicates you must be having more than 7K Regions in Total. As such, the RegionServer are overloaded & WAL Split & Edit Replay would be Slow.    There are RegionOpening Thread, which can be Increased yet the Ideal Solution would be to Reduce the RegionCount or Increase RegionServer Count to ~300-400 Region/RegionServer.    - Smarak ... View more

Hi @kumarkeshav    Your Observation is Correct. The Config isn't exposed via Ambari v2.7.x yet adding the same via Custom HBase-Site.XML is prohibited with the " This property is already defined in this configuration file" message. The same isn't an issue with Ambari v2.6.x, wherein the concerned Write Limit is exposed.    I am not familiar with the Exact Location in Ambari DB, wherein the concerned Parameter is exposed to be manually over-written. The Simplest Solution is the one you are possibly using i.e. Edit the XML for the RegionServer directly & restart them manually to ensure they are picking up the concerned Updated Configuration. However, this isn't practical in a Large Env unless an Automation Tool is used.    If I come across an Easier Fix, I shall update you in the Post.    - Smarak ... View more