Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 6 Jun 2017 05:23:18 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13077456.1496707860000.1364.1496726598175@Atlassian.JIRA>
In-Reply-To: <JIRA.13077456.1496707860000@Atlassian.JIRA>
References: <JIRA.13077456.1496707860000@Atlassian.JIRA> <JIRA.13077456.1496707860964@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-18166) [AMv2] We are splitting
 already-split files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Jun 2017 05:23:22 -0000


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

stack updated HBASE-18166:
--------------------------
    Attachment: HBASE-18166.master.002.patch

> [AMv2] We are splitting already-split files
> -------------------------------------------
>
>                 Key: HBASE-18166
>                 URL: https://issues.apache.org/jira/browse/HBASE-18166
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0
>
>         Attachments: HBASE-18166.master.001.patch, HBASE-18166.master.002.patch
>
>
> Interesting issue. The below adds a lag cleaning up files after a compaction in case of on-going Scanners (for read replicas/offheap).
> HBASE-14970 Backport HBASE-13082 and its sub-jira to branch-1 - recommit (Ram)
> What the lag means is that now that split is run from the HMaster in master branch, when it goes to get a listing of the files to split, it can pick up files that are for archiving but that have not been archived yet.  When it does, it goes ahead and splits them... making references of references.
> Its a mess.
> I added asking the Region if it is splittable a while back. The Master calls this from SplitTableRegionProcedure during preparation. If the RegionServer asked for the split, it is sort of redundant work given the RS asks itself if any references still; if any, it'll wait before asking for a split. But if a user/client asks, then this isSplittable over RPC comes in handy.
> I was thinking that isSplittable could return list of files.... 
> Or, easier, given we know a region is Splittable by the time we go to split the files, then I think master-side we can just skip any references found presuming read-for-archive.
> Will be back with a patch. Want to test on cluster first (Side-effect is regions are offline because file at end of the reference to a reference is removed ... and so the open fails).


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)