Hello @priyanshu_soni    You can skip the "Timestamp" part as the same is inserted by HBase implicitly. I tried the same Query as you, excluding the Timestamp & the same was Successful:   hbase(main):018:0> put 'Table_X1','125','Cf1:CheckItem','{"ID" : "1334134","Name" : "Apparel Fabric","Path" : "Arts, Crafts & Sewing/Fabric/Apparel Fabric"}' Took 0.0077 seconds hbase(main):019:0> scan 'Table_X1' ROW COLUMN+CELL 125 column=Cf1:CheckItem, timestamp=1621593487680, value={"ID" : "1334134","Name" : "Apparel Fabric","Path" : "Arts, Crafts & Sewing/Fabric/Apparel Fabric"} 1 row(s) Took 0.0057 seconds As you may see above, the "timestamp" field corresponds to the Epoch Timestamp of the Inserted Row Time of Operation. If you wish to explicitly specify the Timestamp, You can include a EpochTime as shared below: hbase(main):020:0> put 'Table_X1','126','Cf1:CheckItem','{"ID" : "1334134","Name" : "Apparel Fabric","Path" : "Arts, Crafts & Sewing/Fabric/Apparel Fabric"}',1621593487680 Took 0.0202 seconds hbase(main):021:0> scan 'Table_X1' ROW COLUMN+CELL 125 column=Cf1:CheckItem, timestamp=1621593487680, value={"ID" : "1334134","Name" : "Apparel Fabric","Path" : "Arts, Crafts & Sewing/Fabric/Apparel Fabric"} 126 column=Cf1:CheckItem, timestamp=1621593487680, value={"ID" : "1334134","Name" : "Apparel Fabric","Path" : "Arts, Crafts & Sewing/Fabric/Apparel Fabric"} 2 row(s) Took 0.0071 seconds   Let us know if you have any issues with the Put Operation.   - Smarak ... View more

Hello @nilk    Thanks for using Cloudera Community. Based on the Post, Your Team is experiencing frequent "Bad Health" alerting for various Services, which persists until Restart only to reappear after 1 Minute.    It's likely the Health Test are failing owing to a persistent reason rather than intermittent cause. As you haven't shared the CM Version or CDH Version, Sharing a Link [1] which covers the various Health Test & their Causes. Each Alert have their reasoning & we can review the Alerting on CM UI while implementing the preventive measures. Link [2] shares a Post with similar context, wherein the Steps for each Service Health Alert would be different.   Unfortunately, there is no Single Solution likely for each Service Alerting. As such, Review the Alerting context for each Service, Do post here if you have any queries concerning the reasoning for any specific alerting & proceed accordingly.   - Smarak   [1] https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_ht.html [2] https://community.cloudera.com/t5/Support-Questions/Bad-Health-of-cloudera-Managger/m-p/37161/highlight/true#M37913 ... View more

Hello @vishal6196    It's been a while on the Post yet as far as I recall, the App was writing to 1 CF only. In short, WAL is used for each RegionServer & subsequently, the Writes arrives at MemStore based on CF demarcation at Region Level. From WALReader, We confirmed the WAL have entries for 1 CF only, naturally indicating the MemStore of the concerned CF would be populated only. Additionally, I don't recall Crash being observed.   Are you facing similar concerns in your Environment. If Yes, Kindly share the following details in a New Post: What's the MemStore Flush failure trace from Logs, If the Problem is Persistent, Whether WALReader (Link [1]) shows Writes happening on all CF of the Regions & Count of CF of the Region. - Smarak   [1] https://hbase.apache.org/book.html#hlog_tool.prettyprint ... View more

Hello @WayneWang    As we haven't received any further Update, We are closing the Post assuming the issue was handled by the Steps shared above [1]. In HBase v1.x, We have limited choices with HBase v2.x using a new AssignmentManager (Details in HBASE-12439), which would assist in managing the RIT without ZooKeeper involvement.   Thanks for using Cloudera Community.   - Smarak   [1] https://community.cloudera.com/t5/Support-Questions/Hbase-How-to-fix-failed-regions/m-p/312263/highlight/true#M225066 ... View more

Hello @SurajP    KIndly confirm the issue is resolved. If Yes, Please share the Steps for our fellow Community Members & mark the Post as resolved. If the issue persists, Please share the ZooKeeper Logs.    - Smarak ... View more

Hello @Kenzan    Thanks for the Update. Typically, Such issues lies with Balancing & the TRACE Logging prints the finer details into the same. Ideally, We should have "StochasticLoadBalancer" as Default & "SimpleLoadBalancer" (Set by your Team) extends on BaseLoadBalancer. Have shared 2 Links documenting the 2 Balancer & their running configurations.   As your issue has been resolved, Kindly mark the Post as Resolved to ensure we close the Post as well.    Thanks again for being a Cloudera Community Members & contributing as well.    - Smarak   [1] https://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/master/balancer/SimpleLoadBalancer.html [2] http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/master/balancer/StochasticLoadBalancer.html ... View more

Thank you very much!!!   ... View more