Re: 2.4.2 RC next week

[Andrew Purtell]

Update: This should be the last update before RC vote thread.  branch-2.4
test results are stable again, for example see
https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/64/
. Some long running ITBLL tests will complete over the weekend.

On Fri, Feb 26, 2021 at 10:59 AM Andrew Purtell  wrote:

> Update: Waiting on completion and commit of replication fixes from Sandeep
> Pal. Expecting to spin the RC next week.
>
> On Tue, Feb 16, 2021 at 1:20 PM Andrew Purtell 
> wrote:
>
>> There will be a RC for 2.4.2 available for voting next week.
>>
>> If you have any pending work and need assistance to get it committed
>> please let me know. A quick review of JIRA status turns up only HBASE-25371
>> as pending.
>>
>> --
>> Best regards,
>> Andrew
>>
>> Words like orphans lost among the crosstalk, meaning torn from truth's
>> decrepit hands
>>- A23, Crosstalk
>>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Invitation to participate in a survey about Apache HBase

[Tan, J.]

Dear HBase contributor,

We are doing research on understanding how developers manage a special kind
of Technical Debt in *Java.*

We kindly ask 15-20 minutes of your time to fill out our survey. To help
you decide whether to fill it in, we clarify two points.

“Why should I answer this survey?”

Your participation is essential for us to correctly understand how
developers manage Technical Debt.

“What is in it for me?”

Your valuable contributions to *HBase* are part of the information we
analyzed for this study. Thus, if you help us further by answering
this survey, there are two immediate benefits:

   - you help to improve the efficiency of maintaining the quality of
   *HBase*.
   - the results will be used to propose recommendations to manage
   technical debt and create tool support.

Here is the link to the survey

.

Thank you for your time and attention.

Kind regards,
Jie Tan, Daniel Feitosa and Paris Avgeriou

Software Engineering and Architecture group 
Faculty of Science and Engineering
University of Groningen, the Netherlands

[jira] [Created] (HBASE-25642) Fix or stop warning about already cached block

[Nick Dimiduk (Jira)]

Nick Dimiduk created HBASE-25642:


 Summary: Fix or stop warning about already cached block
 Key: HBASE-25642
 URL: https://issues.apache.org/jira/browse/HBASE-25642
 Project: HBase
  Issue Type: Improvement
  Components: BlockCache, regionserver
Affects Versions: 2.3.0
Reporter: Nick Dimiduk


Our logs have as a fairly common occurrence:
{noformat}
2021-03-05 22:24:31,034 WARN  [StoreFileOpener-foo-1] hfile.BlockCacheUtil: 
Caching an already cached block: blah.bub. This is harmless and can happen in 
rare cases (see HBASE-8547)
{noformat}

If this is really harmless, why do we log? If it's not actually harmless, let's 
take another pass at fixing this situation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25641) Improve storeFile.jsp performance on really large files

[Nick Dimiduk (Jira)]

Nick Dimiduk created HBASE-25641:


 Summary: Improve storeFile.jsp performance on really large files
 Key: HBASE-25641
 URL: https://issues.apache.org/jira/browse/HBASE-25641
 Project: HBase
  Issue Type: Improvement
  Components: regionserver, UI
Affects Versions: 2.3.0
Reporter: Nick Dimiduk


Since HBASE-7171, we have a nice UI for clicking down into the details of an 
hfile on a regions server. When the store file is really large, the performance 
of this page is quite bad. It can take several minutes to summarize a 30-50gb 
hfile. We can do better.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25640) Support hbase rpc compression for remote rpc only

[Huaxiang Sun (Jira)]

Huaxiang Sun created HBASE-25640:


 Summary: Support hbase rpc compression for remote rpc only
 Key: HBASE-25640
 URL: https://issues.apache.org/jira/browse/HBASE-25640
 Project: HBase
  Issue Type: Improvement
  Components: rpc
Affects Versions: 2.3.4
Reporter: Huaxiang Sun
Assignee: Huaxiang Sun


The purpose of Rpc compression is to save network bandwidth. For local 
communication (both hbase client and RS are on the same node), rpc compression 
is unnecessary as local communication is memory copy only and does not go 
through nic. Rpc compression for local communication will be a waste of cpu 
computation power as compress/decompress is cpu intensive. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25639) meta replica state is not respected during active master switch

[Huaxiang Sun (Jira)]

Huaxiang Sun created HBASE-25639:


 Summary: meta replica state is not respected during active master 
switch
 Key: HBASE-25639
 URL: https://issues.apache.org/jira/browse/HBASE-25639
 Project: HBase
  Issue Type: Bug
  Components: meta replicas
Reporter: Huaxiang Sun
Assignee: Huaxiang Sun


We saw this warning in master log.

WARN org.apache.hadoop.hbase.master.assignment.AssignmentManager: No 
RegionStateNode for hbase:meta,,1_0003 but reported as up on 
server1.example.com,16020,1614958467735; closing...

 

The root cause is that meta replica regions are in zookeeper, and these state 
are not iterated by the new active master so it loses track.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25638) The master local region is constantly major compact

[Sun Xin (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sun Xin resolved HBASE-25638.
-
Resolution: Not A Problem

> The master local region is constantly major compact
> ---
>
> Key: HBASE-25638
> URL: https://issues.apache.org/jira/browse/HBASE-25638
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1, 2.3.4, 2.4.1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
>
> In 
> [MasterRegionFlusherAndCompactor.compact|https://github.com/apache/hbase/blob/830d2895b27fa0cf39a28d3af9673a4126ea8258/hbase-server/src/main/java/org/apache/hadoop/hbase/master/region/MasterRegionFlusherAndCompactor.java#L164],
>  we call region.compact(true) constantly like recursion. This caused a lot of 
> logs to be flushed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25638) The master local region is constantly major compact

[Sun Xin (Jira)]

Sun Xin created HBASE-25638:
---

 Summary: The master local region is constantly major compact
 Key: HBASE-25638
 URL: https://issues.apache.org/jira/browse/HBASE-25638
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.4.1, 2.3.4, 3.0.0-alpha-1
Reporter: Sun Xin
Assignee: Sun Xin


In 
[MasterRegionFlusherAndCompactor.compact|https://github.com/apache/hbase/blob/830d2895b27fa0cf39a28d3af9673a4126ea8258/hbase-server/src/main/java/org/apache/hadoop/hbase/master/region/MasterRegionFlusherAndCompactor.java#L164],
 we call region.compact(true) constantly like recursion. This caused a lot of 
logs to be flushed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25637) Rename method completeCompaction to refreshStoreSizeCount

[Yulin Niu (Jira)]

Yulin Niu created HBASE-25637:
-

 Summary: Rename method completeCompaction to refreshStoreSizeCount
 Key: HBASE-25637
 URL: https://issues.apache.org/jira/browse/HBASE-25637
 Project: HBase
  Issue Type: Improvement
Reporter: Yulin Niu
Assignee: Yulin Niu






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25636) Expost HBCK report as metrics

[Yi Mei (Jira)]

Yi Mei created HBASE-25636:
--

 Summary: Expost HBCK report as metrics
 Key: HBASE-25636
 URL: https://issues.apache.org/jira/browse/HBASE-25636
 Project: HBase
  Issue Type: Improvement
Reporter: Yi Mei


Currently, we have a HBCK Report page in master UI to show the problems of HBCK 
Chore report and CatalogJanitor Consistency report. We can expose these 
problems as metrics, so we can configure an alert.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)