[jira] [Commented] (HBASE-27304) Support using IP to expose master/rs servers for some special scenarios

[ https://issues.apache.org/jira/browse/HBASE-27304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598489#comment-17598489 ] Anoop Sam John commented on HBASE-27304: There is a config at HM and RS side to define the name

[jira] [Commented] (HBASE-26245) Store region server list in master local region

[ https://issues.apache.org/jira/browse/HBASE-26245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520290#comment-17520290 ] Anoop Sam John commented on HBASE-26245: [~zhangduo] fix version There was another issue that

[jira] [Commented] (HBASE-25903) ReadOnlyZKClient APIs - CompletableFuture.get() calls can cause threads to hang forver when ZK client create throws Non IOException

[ https://issues.apache.org/jira/browse/HBASE-25903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519370#comment-17519370 ] Anoop Sam John commented on HBASE-25903: >What would be the best way of getting the fix from

[jira] [Commented] (HBASE-26884) Find unavailable regions by the startcode checking on hmaster start up and reassign them

[ https://issues.apache.org/jira/browse/HBASE-26884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17513231#comment-17513231 ] Anoop Sam John commented on HBASE-26884: Exact which version you have seen this? > Find

[jira] [Commented] (HBASE-26699) hbase regionserver keep on restarting in azure setup

[ https://issues.apache.org/jira/browse/HBASE-26699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480858#comment-17480858 ] Anoop Sam John commented on HBASE-26699: Yes DN is DataNode. What about the DN disk volume?

[jira] [Commented] (HBASE-26630) When using SingleColumnValueFilter in TableSnapshotInputFormat, there was a problem that the job was terminated in the middle.

[ https://issues.apache.org/jira/browse/HBASE-26630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477612#comment-17477612 ] Anoop Sam John commented on HBASE-26630: Pls raise the fix as a PR > When using

[jira] [Commented] (HBASE-26552) Introduce retry to logroller when encounters IOException

[ https://issues.apache.org/jira/browse/HBASE-26552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477558#comment-17477558 ] Anoop Sam John commented on HBASE-26552: Can u give a detailed proposal pls? Like different

[jira] [Commented] (HBASE-26557) log4j2 has a critical RCE vulnerability

[ https://issues.apache.org/jira/browse/HBASE-26557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456882#comment-17456882 ] Anoop Sam John commented on HBASE-26557: Can u link vulnerability details also here for

[jira] [Commented] (HBASE-26512) Make timestamp format configurable in HBase shell scan output

[ https://issues.apache.org/jira/browse/HBASE-26512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452189#comment-17452189 ] Anoop Sam John commented on HBASE-26512: On a patch version 2.4.9 and minor version 2.5.0, we

[jira] [Commented] (HBASE-26482) HMaster may clean wals that is replicating in rare cases

[ https://issues.apache.org/jira/browse/HBASE-26482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450014#comment-17450014 ] Anoop Sam John commented on HBASE-26482: bq. JIRA: HBASE-12865 Has fixed this problem.

[jira] [Updated] (HBASE-26465) MemStoreLAB may be released early when its SegmentScanner is scanning

[ https://issues.apache.org/jira/browse/HBASE-26465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26465: --- Affects Version/s: 3.0.0-alpha-2 (was: 3.0.0-alpha-1) >

[jira] [Updated] (HBASE-26465) MemStoreLAB may be released early when its SegmentScanner is scanning

[ https://issues.apache.org/jira/browse/HBASE-26465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26465: --- Affects Version/s: 2.5.0 (was: 2.4.8) > MemStoreLAB may be

[jira] [Updated] (HBASE-26465) MemStoreLAB may be released early when its SegmentScanner is scanning

[ https://issues.apache.org/jira/browse/HBASE-26465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26465: --- Fix Version/s: 2.5.0 3.0.0-alpha-2 > MemStoreLAB may be released early

[jira] [Commented] (HBASE-26337) Optimization for weighted random generators

[ https://issues.apache.org/jira/browse/HBASE-26337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440914#comment-17440914 ] Anoop Sam John commented on HBASE-26337: When we dont care/consider the locality aspect (Cloud

[jira] [Commented] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[ https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433291#comment-17433291 ] Anoop Sam John commented on HBASE-26190: Changing the code paths so as to make sure

[jira] [Commented] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[ https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432791#comment-17432791 ] Anoop Sam John commented on HBASE-26190: With a quick look, I can see we are not populating

[jira] [Commented] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[ https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432786#comment-17432786 ] Anoop Sam John commented on HBASE-26190: We are setting the tableName and CF name in

[jira] [Commented] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[ https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430382#comment-17430382 ] Anoop Sam John commented on HBASE-26190: Pushed to master and branch-2. Thanks

[jira] [Commented] (HBASE-24833) Bootstrap should not delete the META table directory if it's not partial

[ https://issues.apache.org/jira/browse/HBASE-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429302#comment-17429302 ] Anoop Sam John commented on HBASE-24833: Any plan to commit this to 2.4 line also? > Bootstrap

[jira] [Commented] (HBASE-26312) Shell scan fails with timestamp

[ https://issues.apache.org/jira/browse/HBASE-26312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427658#comment-17427658 ] Anoop Sam John commented on HBASE-26312: Thanks.. I thought it was applied only on master. >

[jira] [Updated] (HBASE-26312) Shell scan fails with timestamp

[ https://issues.apache.org/jira/browse/HBASE-26312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26312: --- Fix Version/s: (was: 2.4.8) (was: 2.5.0) > Shell scan fails with

[jira] [Updated] (HBASE-26312) Shell scan fails with timestamp

[ https://issues.apache.org/jira/browse/HBASE-26312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26312: --- Affects Version/s: 3.0.0-alpha-2 > Shell scan fails with timestamp >

[jira] [Commented] (HBASE-26312) scan failed with timestamp

[ https://issues.apache.org/jira/browse/HBASE-26312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423919#comment-17423919 ] Anoop Sam John commented on HBASE-26312: Can u pls raise a Pull request for the fix? > scan

[jira] [Commented] (HBASE-24601) Change default Hfile storage policy from HOT to NONE for HDFS

[ https://issues.apache.org/jira/browse/HBASE-24601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423758#comment-17423758 ] Anoop Sam John commented on HBASE-24601: Better we can mark this as an incompatible change?

[jira] [Commented] (HBASE-26287) the initialization of master could not be completed when hbase:namesapce' region is not online

[ https://issues.apache.org/jira/browse/HBASE-26287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419556#comment-17419556 ] Anoop Sam John commented on HBASE-26287: Why the SSH for the old RS (where NS region) not

[jira] [Commented] (HBASE-24833) Bootstrap should not delete the META table directory if it's not partial

[ https://issues.apache.org/jira/browse/HBASE-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407255#comment-17407255 ] Anoop Sam John commented on HBASE-24833: That change of storing META location in master local

[jira] [Commented] (HBASE-26199) hbck2 should support remove deleted meta region

[ https://issues.apache.org/jira/browse/HBASE-26199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17403176#comment-17403176 ] Anoop Sam John commented on HBASE-26199: These are due to bugs in 2.x initial versions. There a

[jira] [Commented] (HBASE-23584) Decrease rpc getFileStatus count when open a storefile (cache filestatus in storefileinfo rather than load each time)

[ https://issues.apache.org/jira/browse/HBASE-23584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401448#comment-17401448 ] Anoop Sam John commented on HBASE-23584: I came across such a need recently. This is more

[jira] [Commented] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[ https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399558#comment-17399558 ] Anoop Sam John commented on HBASE-26190: Andy, as it was unassigned, I assigned to Kulwant. >

[jira] [Assigned] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[ https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John reassigned HBASE-26190: -- Assignee: Kulwant Singh > High rate logging of BucketAllocatorException: Allocation

[jira] [Commented] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[ https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399500#comment-17399500 ] Anoop Sam John commented on HBASE-26190: +1. We already have stats collection at BC and print

[jira] [Commented] (HBASE-26193) Do not store meta region location as permanent state on zookeeper

[ https://issues.apache.org/jira/browse/HBASE-26193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399488#comment-17399488 ] Anoop Sam John commented on HBASE-26193: Keeping the WAL directory and making sure that is

[jira] [Commented] (HBASE-26092) JVM core dump in the replication path

[ https://issues.apache.org/jira/browse/HBASE-26092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17393718#comment-17393718 ] Anoop Sam John commented on HBASE-26092: One doubt now is this In ReplicationSink side, we

[jira] [Commented] (HBASE-26160) Configurable disallowlist for live editing of loglevels

[ https://issues.apache.org/jira/browse/HBASE-26160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17393581#comment-17393581 ] Anoop Sam John commented on HBASE-26160: Pls fill the Release Notes with new config and how to

[jira] [Commented] (HBASE-26160) Configurable disallowlist for live editing of loglevels

[ https://issues.apache.org/jira/browse/HBASE-26160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17391312#comment-17391312 ] Anoop Sam John commented on HBASE-26160: Whether the deny list should take some pattern instead

[jira] [Comment Edited] (HBASE-26160) Configurable disallowlist for live editing of loglevels

[ https://issues.apache.org/jira/browse/HBASE-26160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17391312#comment-17391312 ] Anoop Sam John edited comment on HBASE-26160 at 8/2/21, 5:07 AM: -

[jira] [Commented] (HBASE-26145) Update fails with DoNotRetryIOException while the region is being split

[ https://issues.apache.org/jira/browse/HBASE-26145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17391306#comment-17391306 ] Anoop Sam John commented on HBASE-26145: At a high level look at HRegion class based on the case

[jira] [Commented] (HBASE-26092) JVM core dump in the replication path

[ https://issues.apache.org/jira/browse/HBASE-26092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17390717#comment-17390717 ] Anoop Sam John commented on HBASE-26092: I made changes in ReplicationSink code (Just for test)

[jira] [Assigned] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John reassigned HBASE-26114: -- Assignee: Jingxuan Fu > when “hbase.mob.compaction.threads.max” is set to a negative

[jira] [Updated] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26114: --- Fix Version/s: (was: 3.0.0-alpha-2) Hadoop Flags: Reviewed Resolution: Fixed

[jira] [Commented] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389305#comment-17389305 ] Anoop Sam John commented on HBASE-26114: I see. Keep the change in branch-2 only then > when

[jira] [Commented] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17389266#comment-17389266 ] Anoop Sam John commented on HBASE-26114: We use PR flow to merge changes. I can see u raised one

[jira] [Updated] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26114: --- Fix Version/s: 3.0.0-alpha-2 2.5.0 > when

[jira] [Assigned] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John reassigned HBASE-26114: -- Assignee: (was: Anoop Sam John) > when “hbase.mob.compaction.threads.max” is set

[jira] [Assigned] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John reassigned HBASE-26114: -- Assignee: Anoop Sam John > when “hbase.mob.compaction.threads.max” is set to a

[jira] [Commented] (HBASE-26092) JVM core dump in the replication path

[ https://issues.apache.org/jira/browse/HBASE-26092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388720#comment-17388720 ] Anoop Sam John commented on HBASE-26092: The replicateWALEntry request is reached at an RS and

[jira] [Commented] (HBASE-26146) Allow custom opts for hbck in hbase bin

[ https://issues.apache.org/jira/browse/HBASE-26146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388423#comment-17388423 ] Anoop Sam John commented on HBASE-26146: Can you pls add details to Release Notes. How to pass

[jira] [Commented] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388177#comment-17388177 ] Anoop Sam John commented on HBASE-26114: [~fujx] u can provide a PR for the change > when

[jira] [Commented] (HBASE-26142) NullPointerException when set 'hbase.hregion.memstore.mslab.indexchunksize.percent' to zero

[ https://issues.apache.org/jira/browse/HBASE-26142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387905#comment-17387905 ] Anoop Sam John commented on HBASE-26142: what is the default BB pool size that this index chunk

[jira] [Updated] (HBASE-26114) when “hbase.mob.compaction.threads.max” is set to a negative number, HMaster cannot start normally

[ https://issues.apache.org/jira/browse/HBASE-26114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26114: --- Priority: Minor (was: Major) > when “hbase.mob.compaction.threads.max” is set to a

[jira] [Commented] (HBASE-24734) RegionInfo#containsRange should support check meta table

[ https://issues.apache.org/jira/browse/HBASE-24734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385272#comment-17385272 ] Anoop Sam John commented on HBASE-24734: Got it. Thanks for explaining. >

[jira] [Commented] (HBASE-26062) SIGSEGV in AsyncFSWAL consume

[ https://issues.apache.org/jira/browse/HBASE-26062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385232#comment-17385232 ] Anoop Sam John commented on HBASE-26062: [~stack] no ASYNC_WAL durability? If so we have other

[jira] [Commented] (HBASE-25701) RegionServer JVM crash when append wal entry

[ https://issues.apache.org/jira/browse/HBASE-25701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385229#comment-17385229 ] Anoop Sam John commented on HBASE-25701: [~jutia] Looks like HBASE-24984 fix will fix ur case.

[jira] [Updated] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

[ https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-24984: --- Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch

[jira] [Updated] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

[ https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-24984: --- Affects Version/s: (was: 2.1.6) 2.0.0 > WAL corruption due to

[jira] [Updated] (HBASE-26088) conn.getBufferedMutator(tableName) leaks thread executors and other problems

[ https://issues.apache.org/jira/browse/HBASE-26088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26088: --- Affects Version/s: (was: 2.4.4) (was: 1.4.13)

[jira] [Updated] (HBASE-26088) conn.getBufferedMutator(tableName) leaks thread executors and other problems

[ https://issues.apache.org/jira/browse/HBASE-26088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26088: --- Release Note: The API doc for Connection#getBufferedMutator(TableName) and

[jira] [Resolved] (HBASE-26088) conn.getBufferedMutator(tableName) leaks thread executors and other problems

[ https://issues.apache.org/jira/browse/HBASE-26088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John resolved HBASE-26088. Fix Version/s: 2.3.6 Hadoop Flags: Reviewed Resolution: Fixed Pushed to

[jira] [Comment Edited] (HBASE-25986) Expose the NORMALIZARION_ENABLED table descriptor through a property in hbase-site

[ https://issues.apache.org/jira/browse/HBASE-25986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383319#comment-17383319 ] Anoop Sam John edited comment on HBASE-25986 at 7/19/21, 12:52 PM: --- RN

[jira] [Commented] (HBASE-25986) Expose the NORMALIZARION_ENABLED table descriptor through a property in hbase-site

[ https://issues.apache.org/jira/browse/HBASE-25986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383319#comment-17383319 ] Anoop Sam John commented on HBASE-25986: RN pls with explanation of new configs > Expose the

[jira] [Commented] (HBASE-26092) JVM core dump in the replication path

[ https://issues.apache.org/jira/browse/HBASE-26092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381760#comment-17381760 ] Anoop Sam John commented on HBASE-26092: In case used SimpleRPCClient instead of Netty client,

[jira] [Commented] (HBASE-24734) Wrong comparator opening Region when 'split-to-WAL' enabled.

[ https://issues.apache.org/jira/browse/HBASE-24734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381757#comment-17381757 ] Anoop Sam John commented on HBASE-24734: I think we should fix it the other way around. META

[jira] [Commented] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

[ https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381739#comment-17381739 ] Anoop Sam John commented on HBASE-24984: There is some diff when it is FSHLog or AsyncFSWAL. In

[jira] [Commented] (HBASE-25985) ReplicationSourceWALReader#run - Reset sleepMultiplier in loop once out of any IOE

[ https://issues.apache.org/jira/browse/HBASE-25985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381538#comment-17381538 ] Anoop Sam John commented on HBASE-25985: No [~stack]. I believe I have not committed it as Duo

[jira] [Commented] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

[ https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381537#comment-17381537 ] Anoop Sam John commented on HBASE-24984: [~huaxiangsun] You are using Netty RPC server right?

[jira] [Commented] (HBASE-26089) Support RegionCoprocessor on CompactionServer

[ https://issues.apache.org/jira/browse/HBASE-26089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381327#comment-17381327 ] Anoop Sam John commented on HBASE-26089: U want to support CPs in CompactionServer? Can we

[jira] [Commented] (HBASE-26083) L1 miss metric is incorrect when using CombinedBlockCache

[ https://issues.apache.org/jira/browse/HBASE-26083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381094#comment-17381094 ] Anoop Sam John commented on HBASE-26083: Just one comment added. pls eval. Then we are good

[jira] [Commented] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

[ https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381087#comment-17381087 ] Anoop Sam John commented on HBASE-24984: Yes. this is not just multiwal. Even in single RS

[jira] [Commented] (HBASE-26088) conn.getBufferedMutator(tableName) leaks thread executors and other problems

[ https://issues.apache.org/jira/browse/HBASE-26088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381052#comment-17381052 ] Anoop Sam John commented on HBASE-26088: bq.The simplest fix I can think of is removing these 2

[jira] [Commented] (HBASE-26083) In branch-2 & branch-1 L1 miss metric is always 0 when using CombinedBlockCache

[ https://issues.apache.org/jira/browse/HBASE-26083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379222#comment-17379222 ] Anoop Sam John commented on HBASE-26083: Ah.. !! Good catch > In branch-2 & branch-1 L1 miss

[jira] [Commented] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

[ https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376174#comment-17376174 ] Anoop Sam John commented on HBASE-24984: We could write a UT to have a 100% fail case when using

[jira] [Commented] (HBASE-26036) DBB released too early and dirty data for some operations

[ https://issues.apache.org/jira/browse/HBASE-26036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17374617#comment-17374617 ] Anoop Sam John commented on HBASE-26036: In case of get calls from Client layer, the

[jira] [Commented] (HBASE-22923) hbase:meta is assigned to localhost when we downgrade the hbase version

[ https://issues.apache.org/jira/browse/HBASE-22923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17374610#comment-17374610 ] Anoop Sam John commented on HBASE-22923: hbase.min.version.move.system.tables Is this a config

[jira] [Commented] (HBASE-26062) SIGSEGV in AsyncFSWAL consume

[ https://issues.apache.org/jira/browse/HBASE-26062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17374321#comment-17374321 ] Anoop Sam John commented on HBASE-26062: The mentioned traces are from write to WAL so should

[jira] [Commented] (HBASE-25902) 1.x to 2.3.x upgrade does not work; you must install an hbase2 that is earlier than hbase-2.3.0 first

[ https://issues.apache.org/jira/browse/HBASE-25902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373229#comment-17373229 ] Anoop Sam John commented on HBASE-25902: bq.you must install an hbase2 that is earlier than

[jira] [Commented] (HBASE-25596) Fix NPE in ReplicationSourceManager as well as avoid permanently unreplicated data due to EOFException from WAL

[ https://issues.apache.org/jira/browse/HBASE-25596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373170#comment-17373170 ] Anoop Sam John commented on HBASE-25596: Thanks [~zhangduo] Its clear now. > Fix NPE in

[jira] [Commented] (HBASE-26036) DBB released too early in HRegion.get() and dirty data for some operations

[ https://issues.apache.org/jira/browse/HBASE-26036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373168#comment-17373168 ] Anoop Sam John commented on HBASE-26036: Basically the internal calls should reach to Region

[jira] [Commented] (HBASE-25596) Fix NPE in ReplicationSourceManager as well as avoid permanently unreplicated data due to EOFException from WAL

[ https://issues.apache.org/jira/browse/HBASE-25596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373161#comment-17373161 ] Anoop Sam John commented on HBASE-25596: That polish sub task is in right [~zhangduo]? You

[jira] [Commented] (HBASE-26024) Region server JVM Crash - A fatal error has been detected by the Java Runtime Environment

[ https://issues.apache.org/jira/browse/HBASE-26024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371308#comment-17371308 ] Anoop Sam John commented on HBASE-26024: Your version in use is 2.1.9? And its read workloads?

[jira] [Resolved] (HBASE-25985) ReplicationSourceWALReader#run - Reset sleepMultiplier in loop once out of any IOE

[ https://issues.apache.org/jira/browse/HBASE-25985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John resolved HBASE-25985. Resolution: Invalid > ReplicationSourceWALReader#run - Reset sleepMultiplier in loop once

[jira] [Commented] (HBASE-26024) Region server JVM Crash - A fatal error has been detected by the Java Runtime Environment

[ https://issues.apache.org/jira/browse/HBASE-26024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367840#comment-17367840 ] Anoop Sam John commented on HBASE-26024: bq.we used the workaround by switching

[jira] [Commented] (HBASE-26021) HBase 1.7 to 2.4 upgrade issue

[ https://issues.apache.org/jira/browse/HBASE-26021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367200#comment-17367200 ] Anoop Sam John commented on HBASE-26021: Oh.. I was about to ask that Q next.. That means if u

[jira] [Commented] (HBASE-26021) HBase 1.7 to 2.4 upgrade issue

[ https://issues.apache.org/jira/browse/HBASE-26021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367001#comment-17367001 ] Anoop Sam John commented on HBASE-26021: Specific to 2.4.x upgrade? Did u check with 2.3.x? >

[jira] [Updated] (HBASE-26013) Get operations readRows metrics becomes zero after HBASE-25677

[ https://issues.apache.org/jira/browse/HBASE-26013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-26013: --- Priority: Major (was: Minor) > Get operations readRows metrics becomes zero after

[jira] [Commented] (HBASE-26013) Get operations readRows metrics becomes zero after HBASE-25677

[ https://issues.apache.org/jira/browse/HBASE-26013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366366#comment-17366366 ] Anoop Sam John commented on HBASE-26013: An issue with table level read metric right? RS level

[jira] [Commented] (HBASE-25391) Flush directly into data directory, skip rename when committing flush

[ https://issues.apache.org/jira/browse/HBASE-25391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360553#comment-17360553 ] Anoop Sam John commented on HBASE-25391: Can we have a Release Notes pls? So this will be the

[jira] [Commented] (HBASE-24984) WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used with multi operation

[ https://issues.apache.org/jira/browse/HBASE-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359804#comment-17359804 ] Anoop Sam John commented on HBASE-24984: >From ServerCall " The reason why we can not use a

[jira] [Created] (HBASE-25985) ReplicationSourceWALReader#run - Reset sleepMultiplier in loop once out of any IOE

Anoop Sam John created HBASE-25985: -- Summary: ReplicationSourceWALReader#run - Reset sleepMultiplier in loop once out of any IOE Key: HBASE-25985 URL: https://issues.apache.org/jira/browse/HBASE-25985

[jira] [Commented] (HBASE-25891) Remove dependence storing WAL filenames for backup

[ https://issues.apache.org/jira/browse/HBASE-25891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357933#comment-17357933 ] Anoop Sam John commented on HBASE-25891: bq.Since log roll during incremental or full backup is

[jira] [Commented] (HBASE-25596) Fix NPE in ReplicationSourceManager as well as avoid permanently unreplicated data due to EOFException from WAL

[ https://issues.apache.org/jira/browse/HBASE-25596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355881#comment-17355881 ] Anoop Sam John commented on HBASE-25596: [~sandeep.pal] Seems there is a one line issue/miss in

[jira] [Commented] (HBASE-19515) Region server left in online servers list forever if it went down after registering to master and before creating ephemeral node

[ https://issues.apache.org/jira/browse/HBASE-19515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355649#comment-17355649 ] Anoop Sam John commented on HBASE-19515: I believe this is fixed now. HBASE-25032 - Do not

[jira] [Created] (HBASE-25961) Backport HBASE-25596 to branch-2.3

Anoop Sam John created HBASE-25961: -- Summary: Backport HBASE-25596 to branch-2.3 Key: HBASE-25961 URL: https://issues.apache.org/jira/browse/HBASE-25961 Project: HBase Issue Type: Sub-task

[jira] [Updated] (HBASE-25553) It is better for ReplicationTracker.getListOfRegionServers to return ServerName instead of String

[ https://issues.apache.org/jira/browse/HBASE-25553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-25553: --- Issue Type: Improvement (was: Umbrella) > It is better for

[jira] [Issue Comment Deleted] (HBASE-24373) Implement JvmMetrics in HBase instead of using the one in hadoop

[ https://issues.apache.org/jira/browse/HBASE-24373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-24373: --- Comment: was deleted (was: Applied in master only right [~zhangduo]?) > Implement

[jira] [Commented] (HBASE-24373) Implement JvmMetrics in HBase instead of using the one in hadoop

[ https://issues.apache.org/jira/browse/HBASE-24373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355062#comment-17355062 ] Anoop Sam John commented on HBASE-24373: Applied in master only right [~zhangduo]? > Implement

[jira] [Commented] (HBASE-24734) Wrong comparator opening Region when 'split-to-WAL' enabled.

[ https://issues.apache.org/jira/browse/HBASE-24734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355058#comment-17355058 ] Anoop Sam John commented on HBASE-24734: When WAL split happens for META region, we will hit

[jira] [Commented] (HBASE-25891) Remove dependence storing WAL filenames for backup

[ https://issues.apache.org/jira/browse/HBASE-25891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354766#comment-17354766 ] Anoop Sam John commented on HBASE-25891: Sounds good. Thanks. > Remove dependence storing WAL

[jira] [Commented] (HBASE-23634) Enable "Split WAL to HFile" by default

[ https://issues.apache.org/jira/browse/HBASE-23634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354752#comment-17354752 ] Anoop Sam John commented on HBASE-23634: There were some issues around this. Not remembering

[jira] [Commented] (HBASE-25891) Remove dependence storing WAL filenames for backup

[ https://issues.apache.org/jira/browse/HBASE-25891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354381#comment-17354381 ] Anoop Sam John commented on HBASE-25891: Is there a new design doc somewhere? Instead of system

[jira] [Commented] (HBASE-25902) 1.x to 2.3.x upgrade does not work; you must install an hbase2 that is earlier than hbase-2.3.0 first

[ https://issues.apache.org/jira/browse/HBASE-25902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354331#comment-17354331 ] Anoop Sam John commented on HBASE-25902: Ok. That means this Jira issue is present in 2.3.x

  1   2   3   4   5   6   7   8   9   10   >