Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 6 Jan 2017 08:09:59 +0000 (UTC)
From: "Phil Yang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13032494.1483690170000.663247.1483690199556@Atlassian.JIRA>
In-Reply-To: <JIRA.13032494.1483690170000@Atlassian.JIRA>
References: <JIRA.13032494.1483690170000@Atlassian.JIRA> <JIRA.13032494.1483690170470@arcas>
Subject: [jira] [Created] (HBASE-17432) Use less threads to read WAL in
 replication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 06 Jan 2017 08:10:02 -0000

Phil Yang created HBASE-17432:
---------------------------------

             Summary: Use less threads to read WAL in replication
                 Key: HBASE-17432
                 URL: https://issues.apache.org/jira/browse/HBASE-17432
             Project: HBase
          Issue Type: Improvement
          Components: Replication
            Reporter: Phil Yang
            Assignee: Phil Yang
             Fix For: 2.0.0


Now for each peer and each failover source we use different threads to read WAL, which means one WAL file will be read many times if we have many peers. We can read logs in one thread and push them to peers concurrently.

Some cases should be considered. For example, if one of peers is stuck, the reading thread should kick it out of concurrent peers and use an independent thread to read logs for this peer just like old style. If finally this peer's progress catch up other peers, they can be merged back.

Of course, failover threads should still be independent because they read different WAL files.


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