[jira] [Updated] (HBASE-28612) test
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Priority: Minor (was: Major) > test > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug >Reporter: wangxin >Priority: Minor > > 111 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28612) test
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Component/s: (was: Replication) > test > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug >Reporter: wangxin >Priority: Major > > 111 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28612) test
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin resolved HBASE-28612. - Resolution: Abandoned > test > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: wangxin >Priority: Major > > 111 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28612) test
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Labels: (was: pull-request-available) > test > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: wangxin >Priority: Major > > 111 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28612) test
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Summary: test (was: replication quota leak when peer changes) > test > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: wangxin >Priority: Major > Labels: pull-request-available > > 111 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28612) replication quota leak when peer changes
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Description: 111 (was: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. The log is as follows: 2024-05-20 20:00:00,796 WARN [RpcServer.default.FPRWQ.Fifo.read.handler=70,queue=1,port=16020] regionserver.ReplicationSourceShipper: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop. Not cleaning buffer usage. Shipper alive: peer1; Reader alive: false 2024-05-20 20:00:01,351 WARN peer=peer1, can't read more edits from WAL as buffer usage 268435456B exceeds limit 268435456B ) > replication quota leak when peer changes > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: wangxin >Priority: Major > Labels: pull-request-available > > 111 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28612) replication quota leak when peer changes
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Description: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. The log is as follows: 2024-05-20 20:00:00,796 WARN [RpcServer.default.FPRWQ.Fifo.read.handler=70,queue=1,port=16020] regionserver.ReplicationSourceShipper: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop. Not cleaning buffer usage. Shipper alive: peer1; Reader alive: false 2024-05-20 20:00:01,351 WARN peer=peer1, can't read more edits from WAL as buffer usage 268435456B exceeds limit 268435456B was: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. The log is as follows: 2024-05-20 20:00:00,796 WARN [RpcServer.default.FPRWQ.Fifo.read.handler=70,queue=1,port=16020] regionserver.ReplicationSourceShipper: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop. Not cleaning buffer usage. Shipper alive: peer1; Reader alive: false 2024-05-20 20:00:01,351 WARN peer=peer1, can't read more edits from WAL as buffer usage 268435456B exceeds limit 268435456B > replication quota leak when peer changes > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: wangxin >Priority: Major > Labels: pull-request-available > > Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper > thread to stop when peer changes. Not cleaning buffer usage. When the amount > of data written to the table in the peer is relatively large, the quota is > already full and has not been released, resulting in the wall reader being > unable to read new data. > The log is as follows: > 2024-05-20 20:00:00,796 WARN > [RpcServer.default.FPRWQ.Fifo.read.handler=70,queue=1,port=16020] > regionserver.ReplicationSourceShipper: Shipper clearWALEntryBatch method > timed out whilst waiting reader/shipper thread to stop. Not cleaning buffer > usage. Shipper alive: peer1; Reader alive: false > 2024-05-20 20:00:01,351 WARN peer=peer1, can't read more edits from WAL as > buffer usage 268435456B exceeds limit 268435456B > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28612) replication quota leak when peer changes
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Description: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. The log is as follows: 2024-05-20 20:00:00,796 WARN [RpcServer.default.FPRWQ.Fifo.read.handler=70,queue=1,port=16020] regionserver.ReplicationSourceShipper: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop. Not cleaning buffer usage. Shipper alive: peer1; Reader alive: false 2024-05-20 20:00:01,351 WARN peer=peer1, can't read more edits from WAL as buffer usage 268435456B exceeds limit 268435456B was: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. > replication quota leak when peer changes > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: wangxin >Priority: Major > Labels: pull-request-available > > Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper > thread to stop when peer changes. Not cleaning buffer usage. When the amount > of data written to the table in the peer is relatively large, the quota is > already full and has not been released, resulting in the wall reader being > unable to read new data. > The log is as follows: > 2024-05-20 20:00:00,796 WARN > [RpcServer.default.FPRWQ.Fifo.read.handler=70,queue=1,port=16020] > regionserver.ReplicationSourceShipper: Shipper clearWALEntryBatch method > timed out whilst waiting reader/shipper thread to stop. Not cleaning buffer > usage. Shipper alive: peer1; Reader alive: false > 2024-05-20 20:00:01,351 WARN peer=peer1, can't read more edits from WAL as > buffer usage 268435456B exceeds limit 268435456B > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-28612) replication quota leak when peer changes
[ https://issues.apache.org/jira/browse/HBASE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangxin updated HBASE-28612: Description: Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. was:Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. > replication quota leak when peer changes > > > Key: HBASE-28612 > URL: https://issues.apache.org/jira/browse/HBASE-28612 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: wangxin >Priority: Major > Labels: pull-request-available > > Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper > thread to stop when peer changes. Not cleaning buffer usage. When the amount > of data written to the table in the peer is relatively large, the quota is > already full and has not been released, resulting in the wall reader being > unable to read new data. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28612) replication quota leak when peer changes
wangxin created HBASE-28612: --- Summary: replication quota leak when peer changes Key: HBASE-28612 URL: https://issues.apache.org/jira/browse/HBASE-28612 Project: HBase Issue Type: Bug Components: Replication Reporter: wangxin Shipper clearWALEntryBatch method timed out whilst waiting reader/shipper thread to stop when peer changes. Not cleaning buffer usage. When the amount of data written to the table in the peer is relatively large, the quota is already full and has not been released, resulting in the wall reader being unable to read new data. -- This message was sent by Atlassian Jira (v8.20.10#820010)