Sean Busbey | 29 Jun 22:06 2016
Picon

[DISCUSS] issue trackers and recent stability of issues.apache/jira

Heya folks,

ASF hosted JIRA has had a rough go of things over the last few months.
Between the spam attacks impacting both availability and our usage
patterns and whatever has been causing the brown outs over the last
two days, things are impacting at least _my_ ability to make use of
the time I have available for the project.

There are other options available to us as a project; no ASF policy
requires us to use any particular issue tracker or even an ASF hosted
issue tracker at all.

Before I go through the effort to figure out what our requirements
would be for a third party solutions (in terms of user load,
persistence of messages, etc), what's our community temperature on
this issue? Do we have the stomach for a transition?

-
busbey

stack (JIRA | 29 Jun 21:16 2016
Picon

[jira] [Created] (HBASE-16146) Counter is a perf killer

stack created HBASE-16146:
-----------------------------

             Summary: Counter is a perf killer
                 Key: HBASE-16146
                 URL: https://issues.apache.org/jira/browse/HBASE-16146
             Project: HBase
          Issue Type: Sub-task
            Reporter: stack

Doing workloadc, perf shows 10%+ of CPU being spent on counter#add. If I disable some of the hot ones -- see
patch -- I can get 10% more throughput (390k to 440k). Figure something better.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

stack (JIRA | 29 Jun 21:07 2016
Picon

[jira] [Resolved] (HBASE-7067) HBase Get perf improvements


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

stack resolved HBASE-7067.
--------------------------
    Resolution: Won't Fix

Resolving umbrella as won't fix though one outstanding issue. Will move it out to be standalone issue. This
is an old umbrella and a bunch has changed since it was filed.

> HBase Get perf improvements
> ---------------------------
>
>                 Key: HBASE-7067
>                 URL: https://issues.apache.org/jira/browse/HBASE-7067
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Karthik Ranganathan
>            Assignee: Karthik Ranganathan
>
> Umbrella task for improving Get performance.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

stack (JIRA | 29 Jun 21:06 2016
Picon

[jira] [Resolved] (HBASE-7100) Allow multiple connections from HBaseClient to each remote endpoint


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

stack resolved HBASE-7100.
--------------------------
    Resolution: Won't Fix

Old. Won't resolve. Easier to start up many Connections now compared to back in 2012.

> Allow multiple connections from HBaseClient to each remote endpoint
> -------------------------------------------------------------------
>
>                 Key: HBASE-7100
>                 URL: https://issues.apache.org/jira/browse/HBASE-7100
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Karthik Ranganathan
>            Assignee: Karthik Ranganathan
>
> Allowing multiple connections gives a *huge* boost while benchmarking performance. In a production
setup, many nodes query a single regionserver. But one connection is not enough for a single HBase client
to push a single regionserver.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

stack (JIRA | 29 Jun 21:06 2016
Picon

[jira] [Resolved] (HBASE-7163) Low-hanging perf improvements in HBase client


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

stack resolved HBASE-7163.
--------------------------
    Resolution: Won't Fix

Old. Code has changed.

> Low-hanging perf  improvements in HBase client
> ----------------------------------------------
>
>                 Key: HBASE-7163
>                 URL: https://issues.apache.org/jira/browse/HBASE-7163
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Karthik Ranganathan
>            Assignee: Karthik Ranganathan
>
> 1. Change cachedRegionsLocations in HConnectionManager from SoftValueSortedMap to ConcurrentSkipListMap:
> This change saves 15% CPU on the client side per profiling. In using the ConcurrentSkipListMap, we can do:
> tableLocations.floorEntry(row).getValue()
> instead of doing:
> SortedMap<byte[], HRegionLocation> matchingRegions =
>         tableLocations.floorEntry(row).getValue();
> if (!matchingRegions.isEmpty()) {
>   HRegionLocation possibleRegion = 
>     matchingRegions.get(matchingRegions.lastKey());
> }
(Continue reading)

Sean Busbey (JIRA | 29 Jun 20:03 2016
Picon

[jira] [Reopened] (HBASE-16093) Splits failed before creating daughter regions leave meta inconsistent


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

Sean Busbey reopened HBASE-16093:
---------------------------------

reopening for backport to branch-1.2 and branch-1.1

> Splits failed before creating daughter regions leave meta inconsistent
> ----------------------------------------------------------------------
>
>                 Key: HBASE-16093
>                 URL: https://issues.apache.org/jira/browse/HBASE-16093
>             Project: HBase
>          Issue Type: Bug
>          Components: master, Region Assignment
>    Affects Versions: 1.3.0, 1.2.1
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Critical
>             Fix For: 1.3.0, 1.4.0
>
>         Attachments: HBASE-16093.branch-1.patch
>
>
> This is on branch-1 based code only.
> Here's the sequence of events.
> # A regionserver opens a new region. That regions looks like it should split.
> # So the regionserver starts a split transaction.
(Continue reading)

Alex (Jitbit | 29 Jun 18:39 2016

"powered by hbase" listing

Hi,

My name is Alex and I'm the founder of Jitbit Software, would love if you
could list our tool on the "powered by HBase" page here:
https://hbase.apache.org/poweredbyhbase.html

Listing details:

Jitbit Helpdesk (https://www.jitbit.com/helpdesk/) is a helpdesk ticketing
system that uses HBase for storage, searching and filtering of ticket and
knowledge-base data. We run HBase on a multinode AWS EC2 cluster, that has
been running in production since 2013, serving more than a 1000 customers.

Thanks a ton!

--

-- 
Alex, Jitbit Software <https://www.jitbit.com/> CEO/Founder
Apache Jenkins Server | 29 Jun 17:04 2016
Picon

Successful: HBase Generate Website

Build status: Successful

If successful, the website and docs have been generated. If failed, skip to the bottom of this email.

Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If
you prefer to keep the hbase-site repo around permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- https://builds.apache.org/job/hbase_generate_website/272/artifact/website.patch.zip
| funzip > 6fb0dd07a81f9e5a109f23c853cd1e0fc1938c2b.patch
  git fetch
  git checkout -b asf-site-6fb0dd07a81f9e5a109f23c853cd1e0fc1938c2b origin/asf-site
  git am --whitespace=fix 6fb0dd07a81f9e5a109f23c853cd1e0fc1938c2b.patch

At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local
asf-site-6fb0dd07a81f9e5a109f23c853cd1e0fc1938c2b branch.

There are lots of spurious changes, such as timestamps and CSS styles in tables, so a generic git diff is not
very useful. To see a list of files that have been added, deleted, renamed, changed type, or are otherwise
interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these commands:
(Continue reading)

Picon

[jira] [Created] (HBASE-16145) MultiRowRangeFilter constructor shouldn't throw IOException

Konstantin Ryakhovskiy created HBASE-16145:
----------------------------------------------

             Summary: MultiRowRangeFilter constructor shouldn't throw IOException
                 Key: HBASE-16145
                 URL: https://issues.apache.org/jira/browse/HBASE-16145
             Project: HBase
          Issue Type: Bug
            Reporter: Konstantin Ryakhovskiy
            Assignee: Konstantin Ryakhovskiy
            Priority: Minor

MultiRowRangeFilter constructor declares IOException.
The constructor:
- sorts and merges incoming arguments - list of ranges, 
- assigns sorted list to a private variable and does not do anything else.
There is no reason to declare IOException.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Phil Yang (JIRA | 29 Jun 08:55 2016
Picon

[jira] [Created] (HBASE-16144) Replication queue's lock will live forever if RS acquiring the lock has dead

Phil Yang created HBASE-16144:
---------------------------------

             Summary: Replication queue's lock will live forever if RS acquiring the lock has dead
                 Key: HBASE-16144
                 URL: https://issues.apache.org/jira/browse/HBASE-16144
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.98.20, 1.1.5, 1.2.1
            Reporter: Phil Yang
            Assignee: Phil Yang

In default, we will use multi operation when we claimQueues from ZK. But if we set
hbase.zookeeper.useMulti=false, we will add a lock first, then copy nodes, finally clean old queue and
the lock. 

However, if the RS acquiring the lock crash before claimQueues done, the lock will always be there and other
RS can never claim the queue.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Picon

[jira] [Created] (HBASE-16143) Change MemstoreScanner constructor to accept List<KeyValueScanner>

ramkrishna.s.vasudevan created HBASE-16143:
----------------------------------------------

             Summary: Change MemstoreScanner constructor to accept List<KeyValueScanner>
                 Key: HBASE-16143
                 URL: https://issues.apache.org/jira/browse/HBASE-16143
             Project: HBase
          Issue Type: Sub-task
    Affects Versions: 2.0.0
            Reporter: ramkrishna.s.vasudevan
            Assignee: ramkrishna.s.vasudevan
            Priority: Minor
             Fix For: 2.0.0

A minor change that helps in creating a memstore that avoids the compaction process and just allows to
creates a pipeline of segments and on flush directly reads the segments in the pipeline and flushes it out
after creating a snapshot of the pipeline. Based on test results and updated patch on HBASE-14921 (to be
provided) will see how much flattening helps us.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Gmane