hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Li (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-17138) Backport read-path offheap (HBASE-11425) to branch-1
Date Mon, 21 Nov 2016 05:15:59 GMT
Yu Li created HBASE-17138:
-----------------------------

             Summary: Backport read-path offheap (HBASE-11425) to branch-1
                 Key: HBASE-17138
                 URL: https://issues.apache.org/jira/browse/HBASE-17138
             Project: HBase
          Issue Type: Bug
            Reporter: Yu Li


>From the [thread|http://mail-archives.apache.org/mod_mbox/hbase-user/201611.mbox/%3CCAM7-19%2Bn7cEiY4H9iLQ3N9V0NXppOPduZwk-hhgNLEaJfiV3kA%40mail.gmail.com%3E]
of sharing our experience and performance data of read-path offheap usage in Alibaba search,
we could see people are positive to have HBASE-11425 in branch-1, so I'd like to create a
JIRA and move the discussion and decision making here.

Echoing some comments from the mail thread:

Bryan:
Is the backported patch available anywhere? If it ends up not getting officially backported
to branch-1 due to 2.0 around the corner, some of us who build our own deploy may want to
integrate into our builds

Andrew:
Yes, please, the patches will be useful to the community even if we decide not to backport
into an official 1.x release.

Enis:
I don't see any reason why we cannot backport to branch-1.

Ted:
Opening a JIRA would be fine. This makes it easier for people to obtain the patch(es)

Nick:
>From the DISCUSS thread re: EOL of 1.1, it seems we'll continue to
support 1.x releases for some time... I would guess these will be
maintained until 2.2 at least. Therefore, offheap patches that have seen
production exposure seem like a reasonable candidate for backport, perhaps in a 1.4 or 1.5
release timeframe.

Anoop:
Because of some compatibility issues, we decide that this will be done in 2.0 only..  Ya as
Andy said, it would be great to share the 1.x backported patches.



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

Mime
View raw message