Replication chunk size

[nipra <pr...@gmail.com>]

Hi,

As per the doc replication happens in a chunk size of 64 MB (default). What
happens in case when this chunk size is not reached for long time (30 mins
or some hours)? Will it cause the changes from master to reach to slave
after a long time? We're planning to use slave cluster as read only cluster
and long delay might not be useful.

Is the chunk size or WAL EOF only criteria for shipping WAL edits to slave
cluster? Or is there a time limit also?

We're using 0.94.6 version.

-- nipra

Re: Replication chunk size

[lars hofhansl <la...@apache.org>]

The replication code continuously reads edits from the WAL and ships them over when (1) there's nothing else to read or (2) the "chunksize" is reached.
The chunksize just limit the maximum size of the RPC request to ship the edits over.

-- Lars


----- Original Message -----
From: nipra <pr...@gmail.com>
To: user@hbase.apache.org
Cc: 
Sent: Saturday, May 24, 2014 7:23 PM
Subject: Replication chunk size

Hi,

As per the doc replication happens in a chunk size of 64 MB (default). What
happens in case when this chunk size is not reached for long time (30 mins
or some hours)? Will it cause the changes from master to reach to slave
after a long time? We're planning to use slave cluster as read only cluster
and long delay might not be useful.

Is the chunk size or WAL EOF only criteria for shipping WAL edits to slave
cluster? Or is there a time limit also?

We're using 0.94.6 version.

-- nipra