You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by gi...@apache.org on 2018/03/21 14:54:13 UTC

[12/51] [partial] hbase-site git commit: Published site at 8ab7b20f48951d77945181024f5e15842bc253c4.

http://git-wip-us.apache.org/repos/asf/hbase-site/blob/6eb695c8/devapidocs/src-html/org/apache/hadoop/hbase/regionserver/wal/FSHLog.RingBufferEventHandler.html
----------------------------------------------------------------------
diff --git a/devapidocs/src-html/org/apache/hadoop/hbase/regionserver/wal/FSHLog.RingBufferEventHandler.html b/devapidocs/src-html/org/apache/hadoop/hbase/regionserver/wal/FSHLog.RingBufferEventHandler.html
index 9971079..03c8b000 100644
--- a/devapidocs/src-html/org/apache/hadoop/hbase/regionserver/wal/FSHLog.RingBufferEventHandler.html
+++ b/devapidocs/src-html/org/apache/hadoop/hbase/regionserver/wal/FSHLog.RingBufferEventHandler.html
@@ -49,1067 +49,1082 @@
 <span class="sourceLineNo">041</span>import org.apache.hadoop.fs.Path;<a name="line.41"></a>
 <span class="sourceLineNo">042</span>import org.apache.hadoop.hbase.HConstants;<a name="line.42"></a>
 <span class="sourceLineNo">043</span>import org.apache.hadoop.hbase.client.RegionInfo;<a name="line.43"></a>
-<span class="sourceLineNo">044</span>import org.apache.hadoop.hbase.trace.TraceUtil;<a name="line.44"></a>
-<span class="sourceLineNo">045</span>import org.apache.hadoop.hbase.util.Bytes;<a name="line.45"></a>
-<span class="sourceLineNo">046</span>import org.apache.hadoop.hbase.util.ClassSize;<a name="line.46"></a>
-<span class="sourceLineNo">047</span>import org.apache.hadoop.hbase.util.FSUtils;<a name="line.47"></a>
-<span class="sourceLineNo">048</span>import org.apache.hadoop.hbase.util.HasThread;<a name="line.48"></a>
-<span class="sourceLineNo">049</span>import org.apache.hadoop.hbase.util.Threads;<a name="line.49"></a>
-<span class="sourceLineNo">050</span>import org.apache.hadoop.hbase.wal.FSHLogProvider;<a name="line.50"></a>
-<span class="sourceLineNo">051</span>import org.apache.hadoop.hbase.wal.WALEdit;<a name="line.51"></a>
-<span class="sourceLineNo">052</span>import org.apache.hadoop.hbase.wal.WALKeyImpl;<a name="line.52"></a>
-<span class="sourceLineNo">053</span>import org.apache.hadoop.hbase.wal.WALProvider.Writer;<a name="line.53"></a>
-<span class="sourceLineNo">054</span>import org.apache.hadoop.hdfs.DFSOutputStream;<a name="line.54"></a>
-<span class="sourceLineNo">055</span>import org.apache.hadoop.hdfs.client.HdfsDataOutputStream;<a name="line.55"></a>
-<span class="sourceLineNo">056</span>import org.apache.hadoop.hdfs.protocol.DatanodeInfo;<a name="line.56"></a>
-<span class="sourceLineNo">057</span>import org.apache.htrace.core.TraceScope;<a name="line.57"></a>
-<span class="sourceLineNo">058</span>import org.apache.yetus.audience.InterfaceAudience;<a name="line.58"></a>
-<span class="sourceLineNo">059</span>import org.slf4j.Logger;<a name="line.59"></a>
-<span class="sourceLineNo">060</span>import org.slf4j.LoggerFactory;<a name="line.60"></a>
-<span class="sourceLineNo">061</span>import org.apache.hbase.thirdparty.com.google.common.annotations.VisibleForTesting;<a name="line.61"></a>
-<span class="sourceLineNo">062</span><a name="line.62"></a>
-<span class="sourceLineNo">063</span>/**<a name="line.63"></a>
-<span class="sourceLineNo">064</span> * The default implementation of FSWAL.<a name="line.64"></a>
-<span class="sourceLineNo">065</span> */<a name="line.65"></a>
-<span class="sourceLineNo">066</span>@InterfaceAudience.Private<a name="line.66"></a>
-<span class="sourceLineNo">067</span>public class FSHLog extends AbstractFSWAL&lt;Writer&gt; {<a name="line.67"></a>
-<span class="sourceLineNo">068</span>  // IMPLEMENTATION NOTES:<a name="line.68"></a>
-<span class="sourceLineNo">069</span>  //<a name="line.69"></a>
-<span class="sourceLineNo">070</span>  // At the core is a ring buffer. Our ring buffer is the LMAX Disruptor. It tries to<a name="line.70"></a>
-<span class="sourceLineNo">071</span>  // minimize synchronizations and volatile writes when multiple contending threads as is the case<a name="line.71"></a>
-<span class="sourceLineNo">072</span>  // here appending and syncing on a single WAL. The Disruptor is configured to handle multiple<a name="line.72"></a>
-<span class="sourceLineNo">073</span>  // producers but it has one consumer only (the producers in HBase are IPC Handlers calling append<a name="line.73"></a>
-<span class="sourceLineNo">074</span>  // and then sync). The single consumer/writer pulls the appends and syncs off the ring buffer.<a name="line.74"></a>
-<span class="sourceLineNo">075</span>  // When a handler calls sync, it is given back a future. The producer 'blocks' on the future so<a name="line.75"></a>
-<span class="sourceLineNo">076</span>  // it does not return until the sync completes. The future is passed over the ring buffer from<a name="line.76"></a>
-<span class="sourceLineNo">077</span>  // the producer/handler to the consumer thread where it does its best to batch up the producer<a name="line.77"></a>
-<span class="sourceLineNo">078</span>  // syncs so one WAL sync actually spans multiple producer sync invocations. How well the<a name="line.78"></a>
-<span class="sourceLineNo">079</span>  // batching works depends on the write rate; i.e. we tend to batch more in times of<a name="line.79"></a>
-<span class="sourceLineNo">080</span>  // high writes/syncs.<a name="line.80"></a>
-<span class="sourceLineNo">081</span>  //<a name="line.81"></a>
-<span class="sourceLineNo">082</span>  // Calls to append now also wait until the append has been done on the consumer side of the<a name="line.82"></a>
-<span class="sourceLineNo">083</span>  // disruptor. We used to not wait but it makes the implementation easier to grok if we have<a name="line.83"></a>
-<span class="sourceLineNo">084</span>  // the region edit/sequence id after the append returns.<a name="line.84"></a>
-<span class="sourceLineNo">085</span>  //<a name="line.85"></a>
-<span class="sourceLineNo">086</span>  // TODO: Handlers need to coordinate appending AND syncing. Can we have the threads contend<a name="line.86"></a>
-<span class="sourceLineNo">087</span>  // once only? Probably hard given syncs take way longer than an append.<a name="line.87"></a>
-<span class="sourceLineNo">088</span>  //<a name="line.88"></a>
-<span class="sourceLineNo">089</span>  // The consumer threads pass the syncs off to multiple syncing threads in a round robin fashion<a name="line.89"></a>
-<span class="sourceLineNo">090</span>  // to ensure we keep up back-to-back FS sync calls (FS sync calls are the long poll writing the<a name="line.90"></a>
-<span class="sourceLineNo">091</span>  // WAL). The consumer thread passes the futures to the sync threads for it to complete<a name="line.91"></a>
-<span class="sourceLineNo">092</span>  // the futures when done.<a name="line.92"></a>
-<span class="sourceLineNo">093</span>  //<a name="line.93"></a>
-<span class="sourceLineNo">094</span>  // The 'sequence' in the below is the sequence of the append/sync on the ringbuffer. It<a name="line.94"></a>
-<span class="sourceLineNo">095</span>  // acts as a sort-of transaction id. It is always incrementing.<a name="line.95"></a>
-<span class="sourceLineNo">096</span>  //<a name="line.96"></a>
-<span class="sourceLineNo">097</span>  // The RingBufferEventHandler class hosts the ring buffer consuming code. The threads that<a name="line.97"></a>
-<span class="sourceLineNo">098</span>  // do the actual FS sync are implementations of SyncRunner. SafePointZigZagLatch is a<a name="line.98"></a>
-<span class="sourceLineNo">099</span>  // synchronization class used to halt the consumer at a safe point -- just after all outstanding<a name="line.99"></a>
-<span class="sourceLineNo">100</span>  // syncs and appends have completed -- so the log roller can swap the WAL out under it.<a name="line.100"></a>
-<span class="sourceLineNo">101</span>  //<a name="line.101"></a>
-<span class="sourceLineNo">102</span>  // We use ring buffer sequence as txid of FSWALEntry and SyncFuture.<a name="line.102"></a>
-<span class="sourceLineNo">103</span>  private static final Logger LOG = LoggerFactory.getLogger(FSHLog.class);<a name="line.103"></a>
-<span class="sourceLineNo">104</span><a name="line.104"></a>
-<span class="sourceLineNo">105</span>  /**<a name="line.105"></a>
-<span class="sourceLineNo">106</span>   * The nexus at which all incoming handlers meet. Does appends and sync with an ordering. Appends<a name="line.106"></a>
-<span class="sourceLineNo">107</span>   * and syncs are each put on the ring which means handlers need to smash up against the ring twice<a name="line.107"></a>
-<span class="sourceLineNo">108</span>   * (can we make it once only? ... maybe not since time to append is so different from time to sync<a name="line.108"></a>
-<span class="sourceLineNo">109</span>   * and sometimes we don't want to sync or we want to async the sync). The ring is where we make<a name="line.109"></a>
-<span class="sourceLineNo">110</span>   * sure of our ordering and it is also where we do batching up of handler sync calls.<a name="line.110"></a>
-<span class="sourceLineNo">111</span>   */<a name="line.111"></a>
-<span class="sourceLineNo">112</span>  private final Disruptor&lt;RingBufferTruck&gt; disruptor;<a name="line.112"></a>
-<span class="sourceLineNo">113</span><a name="line.113"></a>
-<span class="sourceLineNo">114</span>  /**<a name="line.114"></a>
-<span class="sourceLineNo">115</span>   * This fellow is run by the above appendExecutor service but it is all about batching up appends<a name="line.115"></a>
-<span class="sourceLineNo">116</span>   * and syncs; it may shutdown without cleaning out the last few appends or syncs. To guard against<a name="line.116"></a>
-<span class="sourceLineNo">117</span>   * this, keep a reference to this handler and do explicit close on way out to make sure all<a name="line.117"></a>
-<span class="sourceLineNo">118</span>   * flushed out before we exit.<a name="line.118"></a>
-<span class="sourceLineNo">119</span>   */<a name="line.119"></a>
-<span class="sourceLineNo">120</span>  private final RingBufferEventHandler ringBufferEventHandler;<a name="line.120"></a>
-<span class="sourceLineNo">121</span><a name="line.121"></a>
-<span class="sourceLineNo">122</span>  /**<a name="line.122"></a>
-<span class="sourceLineNo">123</span>   * FSDataOutputStream associated with the current SequenceFile.writer<a name="line.123"></a>
-<span class="sourceLineNo">124</span>   */<a name="line.124"></a>
-<span class="sourceLineNo">125</span>  private FSDataOutputStream hdfs_out;<a name="line.125"></a>
-<span class="sourceLineNo">126</span><a name="line.126"></a>
-<span class="sourceLineNo">127</span>  // All about log rolling if not enough replicas outstanding.<a name="line.127"></a>
-<span class="sourceLineNo">128</span><a name="line.128"></a>
-<span class="sourceLineNo">129</span>  // Minimum tolerable replicas, if the actual value is lower than it, rollWriter will be triggered<a name="line.129"></a>
-<span class="sourceLineNo">130</span>  private final int minTolerableReplication;<a name="line.130"></a>
-<span class="sourceLineNo">131</span><a name="line.131"></a>
-<span class="sourceLineNo">132</span>  // If live datanode count is lower than the default replicas value,<a name="line.132"></a>
-<span class="sourceLineNo">133</span>  // RollWriter will be triggered in each sync(So the RollWriter will be<a name="line.133"></a>
-<span class="sourceLineNo">134</span>  // triggered one by one in a short time). Using it as a workaround to slow<a name="line.134"></a>
-<span class="sourceLineNo">135</span>  // down the roll frequency triggered by checkLowReplication().<a name="line.135"></a>
-<span class="sourceLineNo">136</span>  private final AtomicInteger consecutiveLogRolls = new AtomicInteger(0);<a name="line.136"></a>
-<span class="sourceLineNo">137</span><a name="line.137"></a>
-<span class="sourceLineNo">138</span>  private final int lowReplicationRollLimit;<a name="line.138"></a>
-<span class="sourceLineNo">139</span><a name="line.139"></a>
-<span class="sourceLineNo">140</span>  // If consecutiveLogRolls is larger than lowReplicationRollLimit,<a name="line.140"></a>
-<span class="sourceLineNo">141</span>  // then disable the rolling in checkLowReplication().<a name="line.141"></a>
-<span class="sourceLineNo">142</span>  // Enable it if the replications recover.<a name="line.142"></a>
-<span class="sourceLineNo">143</span>  private volatile boolean lowReplicationRollEnabled = true;<a name="line.143"></a>
-<span class="sourceLineNo">144</span><a name="line.144"></a>
-<span class="sourceLineNo">145</span>  /** Number of log close errors tolerated before we abort */<a name="line.145"></a>
-<span class="sourceLineNo">146</span>  private final int closeErrorsTolerated;<a name="line.146"></a>
+<span class="sourceLineNo">044</span>import org.apache.hadoop.hbase.regionserver.HRegion;<a name="line.44"></a>
+<span class="sourceLineNo">045</span>import org.apache.hadoop.hbase.trace.TraceUtil;<a name="line.45"></a>
+<span class="sourceLineNo">046</span>import org.apache.hadoop.hbase.util.Bytes;<a name="line.46"></a>
+<span class="sourceLineNo">047</span>import org.apache.hadoop.hbase.util.ClassSize;<a name="line.47"></a>
+<span class="sourceLineNo">048</span>import org.apache.hadoop.hbase.util.FSUtils;<a name="line.48"></a>
+<span class="sourceLineNo">049</span>import org.apache.hadoop.hbase.util.HasThread;<a name="line.49"></a>
+<span class="sourceLineNo">050</span>import org.apache.hadoop.hbase.util.Threads;<a name="line.50"></a>
+<span class="sourceLineNo">051</span>import org.apache.hadoop.hbase.wal.FSHLogProvider;<a name="line.51"></a>
+<span class="sourceLineNo">052</span>import org.apache.hadoop.hbase.wal.WALEdit;<a name="line.52"></a>
+<span class="sourceLineNo">053</span>import org.apache.hadoop.hbase.wal.WALKeyImpl;<a name="line.53"></a>
+<span class="sourceLineNo">054</span>import org.apache.hadoop.hbase.wal.WALProvider.Writer;<a name="line.54"></a>
+<span class="sourceLineNo">055</span>import org.apache.hadoop.hdfs.DFSOutputStream;<a name="line.55"></a>
+<span class="sourceLineNo">056</span>import org.apache.hadoop.hdfs.client.HdfsDataOutputStream;<a name="line.56"></a>
+<span class="sourceLineNo">057</span>import org.apache.hadoop.hdfs.protocol.DatanodeInfo;<a name="line.57"></a>
+<span class="sourceLineNo">058</span>import org.apache.htrace.core.TraceScope;<a name="line.58"></a>
+<span class="sourceLineNo">059</span>import org.apache.yetus.audience.InterfaceAudience;<a name="line.59"></a>
+<span class="sourceLineNo">060</span>import org.slf4j.Logger;<a name="line.60"></a>
+<span class="sourceLineNo">061</span>import org.slf4j.LoggerFactory;<a name="line.61"></a>
+<span class="sourceLineNo">062</span>import org.apache.hbase.thirdparty.com.google.common.annotations.VisibleForTesting;<a name="line.62"></a>
+<span class="sourceLineNo">063</span><a name="line.63"></a>
+<span class="sourceLineNo">064</span>/**<a name="line.64"></a>
+<span class="sourceLineNo">065</span> * The default implementation of FSWAL.<a name="line.65"></a>
+<span class="sourceLineNo">066</span> */<a name="line.66"></a>
+<span class="sourceLineNo">067</span>@InterfaceAudience.Private<a name="line.67"></a>
+<span class="sourceLineNo">068</span>public class FSHLog extends AbstractFSWAL&lt;Writer&gt; {<a name="line.68"></a>
+<span class="sourceLineNo">069</span>  // IMPLEMENTATION NOTES:<a name="line.69"></a>
+<span class="sourceLineNo">070</span>  //<a name="line.70"></a>
+<span class="sourceLineNo">071</span>  // At the core is a ring buffer. Our ring buffer is the LMAX Disruptor. It tries to<a name="line.71"></a>
+<span class="sourceLineNo">072</span>  // minimize synchronizations and volatile writes when multiple contending threads as is the case<a name="line.72"></a>
+<span class="sourceLineNo">073</span>  // here appending and syncing on a single WAL. The Disruptor is configured to handle multiple<a name="line.73"></a>
+<span class="sourceLineNo">074</span>  // producers but it has one consumer only (the producers in HBase are IPC Handlers calling append<a name="line.74"></a>
+<span class="sourceLineNo">075</span>  // and then sync). The single consumer/writer pulls the appends and syncs off the ring buffer.<a name="line.75"></a>
+<span class="sourceLineNo">076</span>  // When a handler calls sync, it is given back a future. The producer 'blocks' on the future so<a name="line.76"></a>
+<span class="sourceLineNo">077</span>  // it does not return until the sync completes. The future is passed over the ring buffer from<a name="line.77"></a>
+<span class="sourceLineNo">078</span>  // the producer/handler to the consumer thread where it does its best to batch up the producer<a name="line.78"></a>
+<span class="sourceLineNo">079</span>  // syncs so one WAL sync actually spans multiple producer sync invocations. How well the<a name="line.79"></a>
+<span class="sourceLineNo">080</span>  // batching works depends on the write rate; i.e. we tend to batch more in times of<a name="line.80"></a>
+<span class="sourceLineNo">081</span>  // high writes/syncs.<a name="line.81"></a>
+<span class="sourceLineNo">082</span>  //<a name="line.82"></a>
+<span class="sourceLineNo">083</span>  // Calls to append now also wait until the append has been done on the consumer side of the<a name="line.83"></a>
+<span class="sourceLineNo">084</span>  // disruptor. We used to not wait but it makes the implementation easier to grok if we have<a name="line.84"></a>
+<span class="sourceLineNo">085</span>  // the region edit/sequence id after the append returns.<a name="line.85"></a>
+<span class="sourceLineNo">086</span>  //<a name="line.86"></a>
+<span class="sourceLineNo">087</span>  // TODO: Handlers need to coordinate appending AND syncing. Can we have the threads contend<a name="line.87"></a>
+<span class="sourceLineNo">088</span>  // once only? Probably hard given syncs take way longer than an append.<a name="line.88"></a>
+<span class="sourceLineNo">089</span>  //<a name="line.89"></a>
+<span class="sourceLineNo">090</span>  // The consumer threads pass the syncs off to multiple syncing threads in a round robin fashion<a name="line.90"></a>
+<span class="sourceLineNo">091</span>  // to ensure we keep up back-to-back FS sync calls (FS sync calls are the long poll writing the<a name="line.91"></a>
+<span class="sourceLineNo">092</span>  // WAL). The consumer thread passes the futures to the sync threads for it to complete<a name="line.92"></a>
+<span class="sourceLineNo">093</span>  // the futures when done.<a name="line.93"></a>
+<span class="sourceLineNo">094</span>  //<a name="line.94"></a>
+<span class="sourceLineNo">095</span>  // The 'sequence' in the below is the sequence of the append/sync on the ringbuffer. It<a name="line.95"></a>
+<span class="sourceLineNo">096</span>  // acts as a sort-of transaction id. It is always incrementing.<a name="line.96"></a>
+<span class="sourceLineNo">097</span>  //<a name="line.97"></a>
+<span class="sourceLineNo">098</span>  // The RingBufferEventHandler class hosts the ring buffer consuming code. The threads that<a name="line.98"></a>
+<span class="sourceLineNo">099</span>  // do the actual FS sync are implementations of SyncRunner. SafePointZigZagLatch is a<a name="line.99"></a>
+<span class="sourceLineNo">100</span>  // synchronization class used to halt the consumer at a safe point -- just after all outstanding<a name="line.100"></a>
+<span class="sourceLineNo">101</span>  // syncs and appends have completed -- so the log roller can swap the WAL out under it.<a name="line.101"></a>
+<span class="sourceLineNo">102</span>  //<a name="line.102"></a>
+<span class="sourceLineNo">103</span>  // We use ring buffer sequence as txid of FSWALEntry and SyncFuture.<a name="line.103"></a>
+<span class="sourceLineNo">104</span>  private static final Logger LOG = LoggerFactory.getLogger(FSHLog.class);<a name="line.104"></a>
+<span class="sourceLineNo">105</span><a name="line.105"></a>
+<span class="sourceLineNo">106</span>  /**<a name="line.106"></a>
+<span class="sourceLineNo">107</span>   * The nexus at which all incoming handlers meet. Does appends and sync with an ordering. Appends<a name="line.107"></a>
+<span class="sourceLineNo">108</span>   * and syncs are each put on the ring which means handlers need to smash up against the ring twice<a name="line.108"></a>
+<span class="sourceLineNo">109</span>   * (can we make it once only? ... maybe not since time to append is so different from time to sync<a name="line.109"></a>
+<span class="sourceLineNo">110</span>   * and sometimes we don't want to sync or we want to async the sync). The ring is where we make<a name="line.110"></a>
+<span class="sourceLineNo">111</span>   * sure of our ordering and it is also where we do batching up of handler sync calls.<a name="line.111"></a>
+<span class="sourceLineNo">112</span>   */<a name="line.112"></a>
+<span class="sourceLineNo">113</span>  private final Disruptor&lt;RingBufferTruck&gt; disruptor;<a name="line.113"></a>
+<span class="sourceLineNo">114</span><a name="line.114"></a>
+<span class="sourceLineNo">115</span>  /**<a name="line.115"></a>
+<span class="sourceLineNo">116</span>   * This fellow is run by the above appendExecutor service but it is all about batching up appends<a name="line.116"></a>
+<span class="sourceLineNo">117</span>   * and syncs; it may shutdown without cleaning out the last few appends or syncs. To guard against<a name="line.117"></a>
+<span class="sourceLineNo">118</span>   * this, keep a reference to this handler and do explicit close on way out to make sure all<a name="line.118"></a>
+<span class="sourceLineNo">119</span>   * flushed out before we exit.<a name="line.119"></a>
+<span class="sourceLineNo">120</span>   */<a name="line.120"></a>
+<span class="sourceLineNo">121</span>  private final RingBufferEventHandler ringBufferEventHandler;<a name="line.121"></a>
+<span class="sourceLineNo">122</span><a name="line.122"></a>
+<span class="sourceLineNo">123</span>  /**<a name="line.123"></a>
+<span class="sourceLineNo">124</span>   * FSDataOutputStream associated with the current SequenceFile.writer<a name="line.124"></a>
+<span class="sourceLineNo">125</span>   */<a name="line.125"></a>
+<span class="sourceLineNo">126</span>  private FSDataOutputStream hdfs_out;<a name="line.126"></a>
+<span class="sourceLineNo">127</span><a name="line.127"></a>
+<span class="sourceLineNo">128</span>  // All about log rolling if not enough replicas outstanding.<a name="line.128"></a>
+<span class="sourceLineNo">129</span><a name="line.129"></a>
+<span class="sourceLineNo">130</span>  // Minimum tolerable replicas, if the actual value is lower than it, rollWriter will be triggered<a name="line.130"></a>
+<span class="sourceLineNo">131</span>  private final int minTolerableReplication;<a name="line.131"></a>
+<span class="sourceLineNo">132</span><a name="line.132"></a>
+<span class="sourceLineNo">133</span>  private final boolean useHsync;<a name="line.133"></a>
+<span class="sourceLineNo">134</span><a name="line.134"></a>
+<span class="sourceLineNo">135</span>  // If live datanode count is lower than the default replicas value,<a name="line.135"></a>
+<span class="sourceLineNo">136</span>  // RollWriter will be triggered in each sync(So the RollWriter will be<a name="line.136"></a>
+<span class="sourceLineNo">137</span>  // triggered one by one in a short time). Using it as a workaround to slow<a name="line.137"></a>
+<span class="sourceLineNo">138</span>  // down the roll frequency triggered by checkLowReplication().<a name="line.138"></a>
+<span class="sourceLineNo">139</span>  private final AtomicInteger consecutiveLogRolls = new AtomicInteger(0);<a name="line.139"></a>
+<span class="sourceLineNo">140</span><a name="line.140"></a>
+<span class="sourceLineNo">141</span>  private final int lowReplicationRollLimit;<a name="line.141"></a>
+<span class="sourceLineNo">142</span><a name="line.142"></a>
+<span class="sourceLineNo">143</span>  // If consecutiveLogRolls is larger than lowReplicationRollLimit,<a name="line.143"></a>
+<span class="sourceLineNo">144</span>  // then disable the rolling in checkLowReplication().<a name="line.144"></a>
+<span class="sourceLineNo">145</span>  // Enable it if the replications recover.<a name="line.145"></a>
+<span class="sourceLineNo">146</span>  private volatile boolean lowReplicationRollEnabled = true;<a name="line.146"></a>
 <span class="sourceLineNo">147</span><a name="line.147"></a>
-<span class="sourceLineNo">148</span>  private final AtomicInteger closeErrorCount = new AtomicInteger();<a name="line.148"></a>
-<span class="sourceLineNo">149</span><a name="line.149"></a>
-<span class="sourceLineNo">150</span>  /**<a name="line.150"></a>
-<span class="sourceLineNo">151</span>   * Exception handler to pass the disruptor ringbuffer. Same as native implementation only it logs<a name="line.151"></a>
-<span class="sourceLineNo">152</span>   * using our logger instead of java native logger.<a name="line.152"></a>
-<span class="sourceLineNo">153</span>   */<a name="line.153"></a>
-<span class="sourceLineNo">154</span>  static class RingBufferExceptionHandler implements ExceptionHandler&lt;RingBufferTruck&gt; {<a name="line.154"></a>
-<span class="sourceLineNo">155</span><a name="line.155"></a>
-<span class="sourceLineNo">156</span>    @Override<a name="line.156"></a>
-<span class="sourceLineNo">157</span>    public void handleEventException(Throwable ex, long sequence, RingBufferTruck event) {<a name="line.157"></a>
-<span class="sourceLineNo">158</span>      LOG.error("Sequence=" + sequence + ", event=" + event, ex);<a name="line.158"></a>
-<span class="sourceLineNo">159</span>      throw new RuntimeException(ex);<a name="line.159"></a>
-<span class="sourceLineNo">160</span>    }<a name="line.160"></a>
-<span class="sourceLineNo">161</span><a name="line.161"></a>
-<span class="sourceLineNo">162</span>    @Override<a name="line.162"></a>
-<span class="sourceLineNo">163</span>    public void handleOnStartException(Throwable ex) {<a name="line.163"></a>
-<span class="sourceLineNo">164</span>      LOG.error(ex.toString(), ex);<a name="line.164"></a>
-<span class="sourceLineNo">165</span>      throw new RuntimeException(ex);<a name="line.165"></a>
-<span class="sourceLineNo">166</span>    }<a name="line.166"></a>
-<span class="sourceLineNo">167</span><a name="line.167"></a>
-<span class="sourceLineNo">168</span>    @Override<a name="line.168"></a>
-<span class="sourceLineNo">169</span>    public void handleOnShutdownException(Throwable ex) {<a name="line.169"></a>
-<span class="sourceLineNo">170</span>      LOG.error(ex.toString(), ex);<a name="line.170"></a>
-<span class="sourceLineNo">171</span>      throw new RuntimeException(ex);<a name="line.171"></a>
-<span class="sourceLineNo">172</span>    }<a name="line.172"></a>
-<span class="sourceLineNo">173</span>  }<a name="line.173"></a>
-<span class="sourceLineNo">174</span><a name="line.174"></a>
-<span class="sourceLineNo">175</span>  /**<a name="line.175"></a>
-<span class="sourceLineNo">176</span>   * Constructor.<a name="line.176"></a>
-<span class="sourceLineNo">177</span>   * @param fs filesystem handle<a name="line.177"></a>
-<span class="sourceLineNo">178</span>   * @param root path for stored and archived wals<a name="line.178"></a>
-<span class="sourceLineNo">179</span>   * @param logDir dir where wals are stored<a name="line.179"></a>
-<span class="sourceLineNo">180</span>   * @param conf configuration to use<a name="line.180"></a>
-<span class="sourceLineNo">181</span>   */<a name="line.181"></a>
-<span class="sourceLineNo">182</span>  public FSHLog(final FileSystem fs, final Path root, final String logDir, final Configuration conf)<a name="line.182"></a>
-<span class="sourceLineNo">183</span>      throws IOException {<a name="line.183"></a>
-<span class="sourceLineNo">184</span>    this(fs, root, logDir, HConstants.HREGION_OLDLOGDIR_NAME, conf, null, true, null, null);<a name="line.184"></a>
-<span class="sourceLineNo">185</span>  }<a name="line.185"></a>
-<span class="sourceLineNo">186</span><a name="line.186"></a>
-<span class="sourceLineNo">187</span>  /**<a name="line.187"></a>
-<span class="sourceLineNo">188</span>   * Create an edit log at the given &lt;code&gt;dir&lt;/code&gt; location. You should never have to load an<a name="line.188"></a>
-<span class="sourceLineNo">189</span>   * existing log. If there is a log at startup, it should have already been processed and deleted<a name="line.189"></a>
-<span class="sourceLineNo">190</span>   * by the time the WAL object is started up.<a name="line.190"></a>
-<span class="sourceLineNo">191</span>   * @param fs filesystem handle<a name="line.191"></a>
-<span class="sourceLineNo">192</span>   * @param rootDir path to where logs and oldlogs<a name="line.192"></a>
-<span class="sourceLineNo">193</span>   * @param logDir dir where wals are stored<a name="line.193"></a>
-<span class="sourceLineNo">194</span>   * @param archiveDir dir where wals are archived<a name="line.194"></a>
-<span class="sourceLineNo">195</span>   * @param conf configuration to use<a name="line.195"></a>
-<span class="sourceLineNo">196</span>   * @param listeners Listeners on WAL events. Listeners passed here will be registered before we do<a name="line.196"></a>
-<span class="sourceLineNo">197</span>   *          anything else; e.g. the Constructor {@link #rollWriter()}.<a name="line.197"></a>
-<span class="sourceLineNo">198</span>   * @param failIfWALExists If true IOException will be thrown if files related to this wal already<a name="line.198"></a>
-<span class="sourceLineNo">199</span>   *          exist.<a name="line.199"></a>
-<span class="sourceLineNo">200</span>   * @param prefix should always be hostname and port in distributed env and it will be URL encoded<a name="line.200"></a>
-<span class="sourceLineNo">201</span>   *          before being used. If prefix is null, "wal" will be used<a name="line.201"></a>
-<span class="sourceLineNo">202</span>   * @param suffix will be url encoded. null is treated as empty. non-empty must start with<a name="line.202"></a>
-<span class="sourceLineNo">203</span>   *          {@link org.apache.hadoop.hbase.wal.AbstractFSWALProvider#WAL_FILE_NAME_DELIMITER}<a name="line.203"></a>
-<span class="sourceLineNo">204</span>   */<a name="line.204"></a>
-<span class="sourceLineNo">205</span>  public FSHLog(final FileSystem fs, final Path rootDir, final String logDir,<a name="line.205"></a>
-<span class="sourceLineNo">206</span>      final String archiveDir, final Configuration conf, final List&lt;WALActionsListener&gt; listeners,<a name="line.206"></a>
-<span class="sourceLineNo">207</span>      final boolean failIfWALExists, final String prefix, final String suffix) throws IOException {<a name="line.207"></a>
-<span class="sourceLineNo">208</span>    super(fs, rootDir, logDir, archiveDir, conf, listeners, failIfWALExists, prefix, suffix);<a name="line.208"></a>
-<span class="sourceLineNo">209</span>    this.minTolerableReplication = conf.getInt("hbase.regionserver.hlog.tolerable.lowreplication",<a name="line.209"></a>
-<span class="sourceLineNo">210</span>      FSUtils.getDefaultReplication(fs, this.walDir));<a name="line.210"></a>
-<span class="sourceLineNo">211</span>    this.lowReplicationRollLimit = conf.getInt("hbase.regionserver.hlog.lowreplication.rolllimit",<a name="line.211"></a>
-<span class="sourceLineNo">212</span>      5);<a name="line.212"></a>
-<span class="sourceLineNo">213</span>    this.closeErrorsTolerated = conf.getInt("hbase.regionserver.logroll.errors.tolerated", 2);<a name="line.213"></a>
-<span class="sourceLineNo">214</span><a name="line.214"></a>
-<span class="sourceLineNo">215</span>    // rollWriter sets this.hdfs_out if it can.<a name="line.215"></a>
-<span class="sourceLineNo">216</span>    rollWriter();<a name="line.216"></a>
+<span class="sourceLineNo">148</span>  /** Number of log close errors tolerated before we abort */<a name="line.148"></a>
+<span class="sourceLineNo">149</span>  private final int closeErrorsTolerated;<a name="line.149"></a>
+<span class="sourceLineNo">150</span><a name="line.150"></a>
+<span class="sourceLineNo">151</span>  private final AtomicInteger closeErrorCount = new AtomicInteger();<a name="line.151"></a>
+<span class="sourceLineNo">152</span><a name="line.152"></a>
+<span class="sourceLineNo">153</span>  /**<a name="line.153"></a>
+<span class="sourceLineNo">154</span>   * Exception handler to pass the disruptor ringbuffer. Same as native implementation only it logs<a name="line.154"></a>
+<span class="sourceLineNo">155</span>   * using our logger instead of java native logger.<a name="line.155"></a>
+<span class="sourceLineNo">156</span>   */<a name="line.156"></a>
+<span class="sourceLineNo">157</span>  static class RingBufferExceptionHandler implements ExceptionHandler&lt;RingBufferTruck&gt; {<a name="line.157"></a>
+<span class="sourceLineNo">158</span><a name="line.158"></a>
+<span class="sourceLineNo">159</span>    @Override<a name="line.159"></a>
+<span class="sourceLineNo">160</span>    public void handleEventException(Throwable ex, long sequence, RingBufferTruck event) {<a name="line.160"></a>
+<span class="sourceLineNo">161</span>      LOG.error("Sequence=" + sequence + ", event=" + event, ex);<a name="line.161"></a>
+<span class="sourceLineNo">162</span>      throw new RuntimeException(ex);<a name="line.162"></a>
+<span class="sourceLineNo">163</span>    }<a name="line.163"></a>
+<span class="sourceLineNo">164</span><a name="line.164"></a>
+<span class="sourceLineNo">165</span>    @Override<a name="line.165"></a>
+<span class="sourceLineNo">166</span>    public void handleOnStartException(Throwable ex) {<a name="line.166"></a>
+<span class="sourceLineNo">167</span>      LOG.error(ex.toString(), ex);<a name="line.167"></a>
+<span class="sourceLineNo">168</span>      throw new RuntimeException(ex);<a name="line.168"></a>
+<span class="sourceLineNo">169</span>    }<a name="line.169"></a>
+<span class="sourceLineNo">170</span><a name="line.170"></a>
+<span class="sourceLineNo">171</span>    @Override<a name="line.171"></a>
+<span class="sourceLineNo">172</span>    public void handleOnShutdownException(Throwable ex) {<a name="line.172"></a>
+<span class="sourceLineNo">173</span>      LOG.error(ex.toString(), ex);<a name="line.173"></a>
+<span class="sourceLineNo">174</span>      throw new RuntimeException(ex);<a name="line.174"></a>
+<span class="sourceLineNo">175</span>    }<a name="line.175"></a>
+<span class="sourceLineNo">176</span>  }<a name="line.176"></a>
+<span class="sourceLineNo">177</span><a name="line.177"></a>
+<span class="sourceLineNo">178</span>  /**<a name="line.178"></a>
+<span class="sourceLineNo">179</span>   * Constructor.<a name="line.179"></a>
+<span class="sourceLineNo">180</span>   * @param fs filesystem handle<a name="line.180"></a>
+<span class="sourceLineNo">181</span>   * @param root path for stored and archived wals<a name="line.181"></a>
+<span class="sourceLineNo">182</span>   * @param logDir dir where wals are stored<a name="line.182"></a>
+<span class="sourceLineNo">183</span>   * @param conf configuration to use<a name="line.183"></a>
+<span class="sourceLineNo">184</span>   */<a name="line.184"></a>
+<span class="sourceLineNo">185</span>  public FSHLog(final FileSystem fs, final Path root, final String logDir, final Configuration conf)<a name="line.185"></a>
+<span class="sourceLineNo">186</span>      throws IOException {<a name="line.186"></a>
+<span class="sourceLineNo">187</span>    this(fs, root, logDir, HConstants.HREGION_OLDLOGDIR_NAME, conf, null, true, null, null);<a name="line.187"></a>
+<span class="sourceLineNo">188</span>  }<a name="line.188"></a>
+<span class="sourceLineNo">189</span><a name="line.189"></a>
+<span class="sourceLineNo">190</span>  /**<a name="line.190"></a>
+<span class="sourceLineNo">191</span>   * Create an edit log at the given &lt;code&gt;dir&lt;/code&gt; location. You should never have to load an<a name="line.191"></a>
+<span class="sourceLineNo">192</span>   * existing log. If there is a log at startup, it should have already been processed and deleted<a name="line.192"></a>
+<span class="sourceLineNo">193</span>   * by the time the WAL object is started up.<a name="line.193"></a>
+<span class="sourceLineNo">194</span>   * @param fs filesystem handle<a name="line.194"></a>
+<span class="sourceLineNo">195</span>   * @param rootDir path to where logs and oldlogs<a name="line.195"></a>
+<span class="sourceLineNo">196</span>   * @param logDir dir where wals are stored<a name="line.196"></a>
+<span class="sourceLineNo">197</span>   * @param archiveDir dir where wals are archived<a name="line.197"></a>
+<span class="sourceLineNo">198</span>   * @param conf configuration to use<a name="line.198"></a>
+<span class="sourceLineNo">199</span>   * @param listeners Listeners on WAL events. Listeners passed here will be registered before we do<a name="line.199"></a>
+<span class="sourceLineNo">200</span>   *          anything else; e.g. the Constructor {@link #rollWriter()}.<a name="line.200"></a>
+<span class="sourceLineNo">201</span>   * @param failIfWALExists If true IOException will be thrown if files related to this wal already<a name="line.201"></a>
+<span class="sourceLineNo">202</span>   *          exist.<a name="line.202"></a>
+<span class="sourceLineNo">203</span>   * @param prefix should always be hostname and port in distributed env and it will be URL encoded<a name="line.203"></a>
+<span class="sourceLineNo">204</span>   *          before being used. If prefix is null, "wal" will be used<a name="line.204"></a>
+<span class="sourceLineNo">205</span>   * @param suffix will be url encoded. null is treated as empty. non-empty must start with<a name="line.205"></a>
+<span class="sourceLineNo">206</span>   *          {@link org.apache.hadoop.hbase.wal.AbstractFSWALProvider#WAL_FILE_NAME_DELIMITER}<a name="line.206"></a>
+<span class="sourceLineNo">207</span>   */<a name="line.207"></a>
+<span class="sourceLineNo">208</span>  public FSHLog(final FileSystem fs, final Path rootDir, final String logDir,<a name="line.208"></a>
+<span class="sourceLineNo">209</span>      final String archiveDir, final Configuration conf, final List&lt;WALActionsListener&gt; listeners,<a name="line.209"></a>
+<span class="sourceLineNo">210</span>      final boolean failIfWALExists, final String prefix, final String suffix) throws IOException {<a name="line.210"></a>
+<span class="sourceLineNo">211</span>    super(fs, rootDir, logDir, archiveDir, conf, listeners, failIfWALExists, prefix, suffix);<a name="line.211"></a>
+<span class="sourceLineNo">212</span>    this.minTolerableReplication = conf.getInt("hbase.regionserver.hlog.tolerable.lowreplication",<a name="line.212"></a>
+<span class="sourceLineNo">213</span>      FSUtils.getDefaultReplication(fs, this.walDir));<a name="line.213"></a>
+<span class="sourceLineNo">214</span>    this.lowReplicationRollLimit = conf.getInt("hbase.regionserver.hlog.lowreplication.rolllimit",<a name="line.214"></a>
+<span class="sourceLineNo">215</span>      5);<a name="line.215"></a>
+<span class="sourceLineNo">216</span>    this.closeErrorsTolerated = conf.getInt("hbase.regionserver.logroll.errors.tolerated", 2);<a name="line.216"></a>
 <span class="sourceLineNo">217</span><a name="line.217"></a>
-<span class="sourceLineNo">218</span>    // This is the 'writer' -- a single threaded executor. This single thread 'consumes' what is<a name="line.218"></a>
-<span class="sourceLineNo">219</span>    // put on the ring buffer.<a name="line.219"></a>
-<span class="sourceLineNo">220</span>    String hostingThreadName = Thread.currentThread().getName();<a name="line.220"></a>
-<span class="sourceLineNo">221</span>    // Using BlockingWaitStrategy. Stuff that is going on here takes so long it makes no sense<a name="line.221"></a>
-<span class="sourceLineNo">222</span>    // spinning as other strategies do.<a name="line.222"></a>
-<span class="sourceLineNo">223</span>    this.disruptor = new Disruptor&lt;&gt;(RingBufferTruck::new,<a name="line.223"></a>
-<span class="sourceLineNo">224</span>        getPreallocatedEventCount(), Threads.getNamedThreadFactory(hostingThreadName + ".append"),<a name="line.224"></a>
-<span class="sourceLineNo">225</span>        ProducerType.MULTI, new BlockingWaitStrategy());<a name="line.225"></a>
-<span class="sourceLineNo">226</span>    // Advance the ring buffer sequence so that it starts from 1 instead of 0,<a name="line.226"></a>
-<span class="sourceLineNo">227</span>    // because SyncFuture.NOT_DONE = 0.<a name="line.227"></a>
-<span class="sourceLineNo">228</span>    this.disruptor.getRingBuffer().next();<a name="line.228"></a>
-<span class="sourceLineNo">229</span>    int maxHandlersCount = conf.getInt(HConstants.REGION_SERVER_HANDLER_COUNT, 200);<a name="line.229"></a>
-<span class="sourceLineNo">230</span>    this.ringBufferEventHandler = new RingBufferEventHandler(<a name="line.230"></a>
-<span class="sourceLineNo">231</span>        conf.getInt("hbase.regionserver.hlog.syncer.count", 5), maxHandlersCount);<a name="line.231"></a>
-<span class="sourceLineNo">232</span>    this.disruptor.setDefaultExceptionHandler(new RingBufferExceptionHandler());<a name="line.232"></a>
-<span class="sourceLineNo">233</span>    this.disruptor.handleEventsWith(new RingBufferEventHandler[] { this.ringBufferEventHandler });<a name="line.233"></a>
-<span class="sourceLineNo">234</span>    // Starting up threads in constructor is a no no; Interface should have an init call.<a name="line.234"></a>
-<span class="sourceLineNo">235</span>    this.disruptor.start();<a name="line.235"></a>
-<span class="sourceLineNo">236</span>  }<a name="line.236"></a>
-<span class="sourceLineNo">237</span><a name="line.237"></a>
-<span class="sourceLineNo">238</span>  /**<a name="line.238"></a>
-<span class="sourceLineNo">239</span>   * Currently, we need to expose the writer's OutputStream to tests so that they can manipulate the<a name="line.239"></a>
-<span class="sourceLineNo">240</span>   * default behavior (such as setting the maxRecoveryErrorCount value for example (see<a name="line.240"></a>
-<span class="sourceLineNo">241</span>   * {@see org.apache.hadoop.hbase.regionserver.wal.AbstractTestWALReplay#testReplayEditsWrittenIntoWAL()}). This is<a name="line.241"></a>
-<span class="sourceLineNo">242</span>   * done using reflection on the underlying HDFS OutputStream. NOTE: This could be removed once Hadoop1 support is<a name="line.242"></a>
-<span class="sourceLineNo">243</span>   * removed.<a name="line.243"></a>
-<span class="sourceLineNo">244</span>   * @return null if underlying stream is not ready.<a name="line.244"></a>
-<span class="sourceLineNo">245</span>   */<a name="line.245"></a>
-<span class="sourceLineNo">246</span>  @VisibleForTesting<a name="line.246"></a>
-<span class="sourceLineNo">247</span>  OutputStream getOutputStream() {<a name="line.247"></a>
-<span class="sourceLineNo">248</span>    FSDataOutputStream fsdos = this.hdfs_out;<a name="line.248"></a>
-<span class="sourceLineNo">249</span>    return fsdos != null ? fsdos.getWrappedStream() : null;<a name="line.249"></a>
-<span class="sourceLineNo">250</span>  }<a name="line.250"></a>
-<span class="sourceLineNo">251</span><a name="line.251"></a>
-<span class="sourceLineNo">252</span>  /**<a name="line.252"></a>
-<span class="sourceLineNo">253</span>   * Run a sync after opening to set up the pipeline.<a name="line.253"></a>
-<span class="sourceLineNo">254</span>   */<a name="line.254"></a>
-<span class="sourceLineNo">255</span>  private void preemptiveSync(final ProtobufLogWriter nextWriter) {<a name="line.255"></a>
-<span class="sourceLineNo">256</span>    long startTimeNanos = System.nanoTime();<a name="line.256"></a>
-<span class="sourceLineNo">257</span>    try {<a name="line.257"></a>
-<span class="sourceLineNo">258</span>      nextWriter.sync();<a name="line.258"></a>
-<span class="sourceLineNo">259</span>      postSync(System.nanoTime() - startTimeNanos, 0);<a name="line.259"></a>
-<span class="sourceLineNo">260</span>    } catch (IOException e) {<a name="line.260"></a>
-<span class="sourceLineNo">261</span>      // optimization failed, no need to abort here.<a name="line.261"></a>
-<span class="sourceLineNo">262</span>      LOG.warn("pre-sync failed but an optimization so keep going", e);<a name="line.262"></a>
-<span class="sourceLineNo">263</span>    }<a name="line.263"></a>
-<span class="sourceLineNo">264</span>  }<a name="line.264"></a>
-<span class="sourceLineNo">265</span><a name="line.265"></a>
-<span class="sourceLineNo">266</span>  /**<a name="line.266"></a>
-<span class="sourceLineNo">267</span>   * This method allows subclasses to inject different writers without having to extend other<a name="line.267"></a>
-<span class="sourceLineNo">268</span>   * methods like rollWriter().<a name="line.268"></a>
-<span class="sourceLineNo">269</span>   * @return Writer instance<a name="line.269"></a>
-<span class="sourceLineNo">270</span>   */<a name="line.270"></a>
-<span class="sourceLineNo">271</span>  @Override<a name="line.271"></a>
-<span class="sourceLineNo">272</span>  protected Writer createWriterInstance(final Path path) throws IOException {<a name="line.272"></a>
-<span class="sourceLineNo">273</span>    Writer writer = FSHLogProvider.createWriter(conf, fs, path, false);<a name="line.273"></a>
-<span class="sourceLineNo">274</span>    if (writer instanceof ProtobufLogWriter) {<a name="line.274"></a>
-<span class="sourceLineNo">275</span>      preemptiveSync((ProtobufLogWriter) writer);<a name="line.275"></a>
-<span class="sourceLineNo">276</span>    }<a name="line.276"></a>
-<span class="sourceLineNo">277</span>    return writer;<a name="line.277"></a>
-<span class="sourceLineNo">278</span>  }<a name="line.278"></a>
-<span class="sourceLineNo">279</span><a name="line.279"></a>
-<span class="sourceLineNo">280</span>  /**<a name="line.280"></a>
-<span class="sourceLineNo">281</span>   * Used to manufacture race condition reliably. For testing only.<a name="line.281"></a>
-<span class="sourceLineNo">282</span>   * @see #beforeWaitOnSafePoint()<a name="line.282"></a>
-<span class="sourceLineNo">283</span>   */<a name="line.283"></a>
-<span class="sourceLineNo">284</span>  @VisibleForTesting<a name="line.284"></a>
-<span class="sourceLineNo">285</span>  protected void afterCreatingZigZagLatch() {<a name="line.285"></a>
-<span class="sourceLineNo">286</span>  }<a name="line.286"></a>
-<span class="sourceLineNo">287</span><a name="line.287"></a>
-<span class="sourceLineNo">288</span>  /**<a name="line.288"></a>
-<span class="sourceLineNo">289</span>   * @see #afterCreatingZigZagLatch()<a name="line.289"></a>
-<span class="sourceLineNo">290</span>   */<a name="line.290"></a>
-<span class="sourceLineNo">291</span>  @VisibleForTesting<a name="line.291"></a>
-<span class="sourceLineNo">292</span>  protected void beforeWaitOnSafePoint() {<a name="line.292"></a>
-<span class="sourceLineNo">293</span>  }<a name="line.293"></a>
-<span class="sourceLineNo">294</span><a name="line.294"></a>
-<span class="sourceLineNo">295</span>  @Override<a name="line.295"></a>
-<span class="sourceLineNo">296</span>  protected void doAppend(Writer writer, FSWALEntry entry) throws IOException {<a name="line.296"></a>
-<span class="sourceLineNo">297</span>    writer.append(entry);<a name="line.297"></a>
+<span class="sourceLineNo">218</span>    this.useHsync = conf.getBoolean(HRegion.WAL_HSYNC_CONF_KEY, HRegion.DEFAULT_WAL_HSYNC);<a name="line.218"></a>
+<span class="sourceLineNo">219</span><a name="line.219"></a>
+<span class="sourceLineNo">220</span>    // rollWriter sets this.hdfs_out if it can.<a name="line.220"></a>
+<span class="sourceLineNo">221</span>    rollWriter();<a name="line.221"></a>
+<span class="sourceLineNo">222</span><a name="line.222"></a>
+<span class="sourceLineNo">223</span>    // This is the 'writer' -- a single threaded executor. This single thread 'consumes' what is<a name="line.223"></a>
+<span class="sourceLineNo">224</span>    // put on the ring buffer.<a name="line.224"></a>
+<span class="sourceLineNo">225</span>    String hostingThreadName = Thread.currentThread().getName();<a name="line.225"></a>
+<span class="sourceLineNo">226</span>    // Using BlockingWaitStrategy. Stuff that is going on here takes so long it makes no sense<a name="line.226"></a>
+<span class="sourceLineNo">227</span>    // spinning as other strategies do.<a name="line.227"></a>
+<span class="sourceLineNo">228</span>    this.disruptor = new Disruptor&lt;&gt;(RingBufferTruck::new,<a name="line.228"></a>
+<span class="sourceLineNo">229</span>        getPreallocatedEventCount(), Threads.getNamedThreadFactory(hostingThreadName + ".append"),<a name="line.229"></a>
+<span class="sourceLineNo">230</span>        ProducerType.MULTI, new BlockingWaitStrategy());<a name="line.230"></a>
+<span class="sourceLineNo">231</span>    // Advance the ring buffer sequence so that it starts from 1 instead of 0,<a name="line.231"></a>
+<span class="sourceLineNo">232</span>    // because SyncFuture.NOT_DONE = 0.<a name="line.232"></a>
+<span class="sourceLineNo">233</span>    this.disruptor.getRingBuffer().next();<a name="line.233"></a>
+<span class="sourceLineNo">234</span>    int maxHandlersCount = conf.getInt(HConstants.REGION_SERVER_HANDLER_COUNT, 200);<a name="line.234"></a>
+<span class="sourceLineNo">235</span>    this.ringBufferEventHandler = new RingBufferEventHandler(<a name="line.235"></a>
+<span class="sourceLineNo">236</span>        conf.getInt("hbase.regionserver.hlog.syncer.count", 5), maxHandlersCount);<a name="line.236"></a>
+<span class="sourceLineNo">237</span>    this.disruptor.setDefaultExceptionHandler(new RingBufferExceptionHandler());<a name="line.237"></a>
+<span class="sourceLineNo">238</span>    this.disruptor.handleEventsWith(new RingBufferEventHandler[] { this.ringBufferEventHandler });<a name="line.238"></a>
+<span class="sourceLineNo">239</span>    // Starting up threads in constructor is a no no; Interface should have an init call.<a name="line.239"></a>
+<span class="sourceLineNo">240</span>    this.disruptor.start();<a name="line.240"></a>
+<span class="sourceLineNo">241</span>  }<a name="line.241"></a>
+<span class="sourceLineNo">242</span><a name="line.242"></a>
+<span class="sourceLineNo">243</span>  /**<a name="line.243"></a>
+<span class="sourceLineNo">244</span>   * Currently, we need to expose the writer's OutputStream to tests so that they can manipulate the<a name="line.244"></a>
+<span class="sourceLineNo">245</span>   * default behavior (such as setting the maxRecoveryErrorCount value for example (see<a name="line.245"></a>
+<span class="sourceLineNo">246</span>   * {@see org.apache.hadoop.hbase.regionserver.wal.AbstractTestWALReplay#testReplayEditsWrittenIntoWAL()}). This is<a name="line.246"></a>
+<span class="sourceLineNo">247</span>   * done using reflection on the underlying HDFS OutputStream. NOTE: This could be removed once Hadoop1 support is<a name="line.247"></a>
+<span class="sourceLineNo">248</span>   * removed.<a name="line.248"></a>
+<span class="sourceLineNo">249</span>   * @return null if underlying stream is not ready.<a name="line.249"></a>
+<span class="sourceLineNo">250</span>   */<a name="line.250"></a>
+<span class="sourceLineNo">251</span>  @VisibleForTesting<a name="line.251"></a>
+<span class="sourceLineNo">252</span>  OutputStream getOutputStream() {<a name="line.252"></a>
+<span class="sourceLineNo">253</span>    FSDataOutputStream fsdos = this.hdfs_out;<a name="line.253"></a>
+<span class="sourceLineNo">254</span>    return fsdos != null ? fsdos.getWrappedStream() : null;<a name="line.254"></a>
+<span class="sourceLineNo">255</span>  }<a name="line.255"></a>
+<span class="sourceLineNo">256</span><a name="line.256"></a>
+<span class="sourceLineNo">257</span>  /**<a name="line.257"></a>
+<span class="sourceLineNo">258</span>   * Run a sync after opening to set up the pipeline.<a name="line.258"></a>
+<span class="sourceLineNo">259</span>   */<a name="line.259"></a>
+<span class="sourceLineNo">260</span>  private void preemptiveSync(final ProtobufLogWriter nextWriter) {<a name="line.260"></a>
+<span class="sourceLineNo">261</span>    long startTimeNanos = System.nanoTime();<a name="line.261"></a>
+<span class="sourceLineNo">262</span>    try {<a name="line.262"></a>
+<span class="sourceLineNo">263</span>      nextWriter.sync(useHsync);<a name="line.263"></a>
+<span class="sourceLineNo">264</span>      postSync(System.nanoTime() - startTimeNanos, 0);<a name="line.264"></a>
+<span class="sourceLineNo">265</span>    } catch (IOException e) {<a name="line.265"></a>
+<span class="sourceLineNo">266</span>      // optimization failed, no need to abort here.<a name="line.266"></a>
+<span class="sourceLineNo">267</span>      LOG.warn("pre-sync failed but an optimization so keep going", e);<a name="line.267"></a>
+<span class="sourceLineNo">268</span>    }<a name="line.268"></a>
+<span class="sourceLineNo">269</span>  }<a name="line.269"></a>
+<span class="sourceLineNo">270</span><a name="line.270"></a>
+<span class="sourceLineNo">271</span>  /**<a name="line.271"></a>
+<span class="sourceLineNo">272</span>   * This method allows subclasses to inject different writers without having to extend other<a name="line.272"></a>
+<span class="sourceLineNo">273</span>   * methods like rollWriter().<a name="line.273"></a>
+<span class="sourceLineNo">274</span>   * @return Writer instance<a name="line.274"></a>
+<span class="sourceLineNo">275</span>   */<a name="line.275"></a>
+<span class="sourceLineNo">276</span>  @Override<a name="line.276"></a>
+<span class="sourceLineNo">277</span>  protected Writer createWriterInstance(final Path path) throws IOException {<a name="line.277"></a>
+<span class="sourceLineNo">278</span>    Writer writer = FSHLogProvider.createWriter(conf, fs, path, false);<a name="line.278"></a>
+<span class="sourceLineNo">279</span>    if (writer instanceof ProtobufLogWriter) {<a name="line.279"></a>
+<span class="sourceLineNo">280</span>      preemptiveSync((ProtobufLogWriter) writer);<a name="line.280"></a>
+<span class="sourceLineNo">281</span>    }<a name="line.281"></a>
+<span class="sourceLineNo">282</span>    return writer;<a name="line.282"></a>
+<span class="sourceLineNo">283</span>  }<a name="line.283"></a>
+<span class="sourceLineNo">284</span><a name="line.284"></a>
+<span class="sourceLineNo">285</span>  /**<a name="line.285"></a>
+<span class="sourceLineNo">286</span>   * Used to manufacture race condition reliably. For testing only.<a name="line.286"></a>
+<span class="sourceLineNo">287</span>   * @see #beforeWaitOnSafePoint()<a name="line.287"></a>
+<span class="sourceLineNo">288</span>   */<a name="line.288"></a>
+<span class="sourceLineNo">289</span>  @VisibleForTesting<a name="line.289"></a>
+<span class="sourceLineNo">290</span>  protected void afterCreatingZigZagLatch() {<a name="line.290"></a>
+<span class="sourceLineNo">291</span>  }<a name="line.291"></a>
+<span class="sourceLineNo">292</span><a name="line.292"></a>
+<span class="sourceLineNo">293</span>  /**<a name="line.293"></a>
+<span class="sourceLineNo">294</span>   * @see #afterCreatingZigZagLatch()<a name="line.294"></a>
+<span class="sourceLineNo">295</span>   */<a name="line.295"></a>
+<span class="sourceLineNo">296</span>  @VisibleForTesting<a name="line.296"></a>
+<span class="sourceLineNo">297</span>  protected void beforeWaitOnSafePoint() {<a name="line.297"></a>
 <span class="sourceLineNo">298</span>  }<a name="line.298"></a>
 <span class="sourceLineNo">299</span><a name="line.299"></a>
 <span class="sourceLineNo">300</span>  @Override<a name="line.300"></a>
-<span class="sourceLineNo">301</span>  protected void doReplaceWriter(Path oldPath, Path newPath, Writer nextWriter) throws IOException {<a name="line.301"></a>
-<span class="sourceLineNo">302</span>    // Ask the ring buffer writer to pause at a safe point. Once we do this, the writer<a name="line.302"></a>
-<span class="sourceLineNo">303</span>    // thread will eventually pause. An error hereafter needs to release the writer thread<a name="line.303"></a>
-<span class="sourceLineNo">304</span>    // regardless -- hence the finally block below. Note, this method is called from the FSHLog<a name="line.304"></a>
-<span class="sourceLineNo">305</span>    // constructor BEFORE the ring buffer is set running so it is null on first time through<a name="line.305"></a>
-<span class="sourceLineNo">306</span>    // here; allow for that.<a name="line.306"></a>
-<span class="sourceLineNo">307</span>    SyncFuture syncFuture = null;<a name="line.307"></a>
-<span class="sourceLineNo">308</span>    SafePointZigZagLatch zigzagLatch = null;<a name="line.308"></a>
-<span class="sourceLineNo">309</span>    long sequence = -1L;<a name="line.309"></a>
-<span class="sourceLineNo">310</span>    if (this.ringBufferEventHandler != null) {<a name="line.310"></a>
-<span class="sourceLineNo">311</span>      // Get sequence first to avoid dead lock when ring buffer is full<a name="line.311"></a>
-<span class="sourceLineNo">312</span>      // Considering below sequence<a name="line.312"></a>
-<span class="sourceLineNo">313</span>      // 1. replaceWriter is called and zigzagLatch is initialized<a name="line.313"></a>
-<span class="sourceLineNo">314</span>      // 2. ringBufferEventHandler#onEvent is called and arrives at #attainSafePoint(long) then wait<a name="line.314"></a>
-<span class="sourceLineNo">315</span>      // on safePointReleasedLatch<a name="line.315"></a>
-<span class="sourceLineNo">316</span>      // 3. Since ring buffer is full, if we get sequence when publish sync, the replaceWriter<a name="line.316"></a>
-<span class="sourceLineNo">317</span>      // thread will wait for the ring buffer to be consumed, but the only consumer is waiting<a name="line.317"></a>
-<span class="sourceLineNo">318</span>      // replaceWriter thread to release safePointReleasedLatch, which causes a deadlock<a name="line.318"></a>
-<span class="sourceLineNo">319</span>      sequence = getSequenceOnRingBuffer();<a name="line.319"></a>
-<span class="sourceLineNo">320</span>      zigzagLatch = this.ringBufferEventHandler.attainSafePoint();<a name="line.320"></a>
-<span class="sourceLineNo">321</span>    }<a name="line.321"></a>
-<span class="sourceLineNo">322</span>    afterCreatingZigZagLatch();<a name="line.322"></a>
-<span class="sourceLineNo">323</span>    try {<a name="line.323"></a>
-<span class="sourceLineNo">324</span>      // Wait on the safe point to be achieved. Send in a sync in case nothing has hit the<a name="line.324"></a>
-<span class="sourceLineNo">325</span>      // ring buffer between the above notification of writer that we want it to go to<a name="line.325"></a>
-<span class="sourceLineNo">326</span>      // 'safe point' and then here where we are waiting on it to attain safe point. Use<a name="line.326"></a>
-<span class="sourceLineNo">327</span>      // 'sendSync' instead of 'sync' because we do not want this thread to block waiting on it<a name="line.327"></a>
-<span class="sourceLineNo">328</span>      // to come back. Cleanup this syncFuture down below after we are ready to run again.<a name="line.328"></a>
-<span class="sourceLineNo">329</span>      try {<a name="line.329"></a>
-<span class="sourceLineNo">330</span>        if (zigzagLatch != null) {<a name="line.330"></a>
-<span class="sourceLineNo">331</span>          // use assert to make sure no change breaks the logic that<a name="line.331"></a>
-<span class="sourceLineNo">332</span>          // sequence and zigzagLatch will be set together<a name="line.332"></a>
-<span class="sourceLineNo">333</span>          assert sequence &gt; 0L : "Failed to get sequence from ring buffer";<a name="line.333"></a>
-<span class="sourceLineNo">334</span>          TraceUtil.addTimelineAnnotation("awaiting safepoint");<a name="line.334"></a>
-<span class="sourceLineNo">335</span>          syncFuture = zigzagLatch.waitSafePoint(publishSyncOnRingBuffer(sequence));<a name="line.335"></a>
-<span class="sourceLineNo">336</span>        }<a name="line.336"></a>
-<span class="sourceLineNo">337</span>      } catch (FailedSyncBeforeLogCloseException e) {<a name="line.337"></a>
-<span class="sourceLineNo">338</span>        // If unflushed/unsynced entries on close, it is reason to abort.<a name="line.338"></a>
-<span class="sourceLineNo">339</span>        if (isUnflushedEntries()) {<a name="line.339"></a>
-<span class="sourceLineNo">340</span>          throw e;<a name="line.340"></a>
+<span class="sourceLineNo">301</span>  protected void doAppend(Writer writer, FSWALEntry entry) throws IOException {<a name="line.301"></a>
+<span class="sourceLineNo">302</span>    writer.append(entry);<a name="line.302"></a>
+<span class="sourceLineNo">303</span>  }<a name="line.303"></a>
+<span class="sourceLineNo">304</span><a name="line.304"></a>
+<span class="sourceLineNo">305</span>  @Override<a name="line.305"></a>
+<span class="sourceLineNo">306</span>  protected void doReplaceWriter(Path oldPath, Path newPath, Writer nextWriter) throws IOException {<a name="line.306"></a>
+<span class="sourceLineNo">307</span>    // Ask the ring buffer writer to pause at a safe point. Once we do this, the writer<a name="line.307"></a>
+<span class="sourceLineNo">308</span>    // thread will eventually pause. An error hereafter needs to release the writer thread<a name="line.308"></a>
+<span class="sourceLineNo">309</span>    // regardless -- hence the finally block below. Note, this method is called from the FSHLog<a name="line.309"></a>
+<span class="sourceLineNo">310</span>    // constructor BEFORE the ring buffer is set running so it is null on first time through<a name="line.310"></a>
+<span class="sourceLineNo">311</span>    // here; allow for that.<a name="line.311"></a>
+<span class="sourceLineNo">312</span>    SyncFuture syncFuture = null;<a name="line.312"></a>
+<span class="sourceLineNo">313</span>    SafePointZigZagLatch zigzagLatch = null;<a name="line.313"></a>
+<span class="sourceLineNo">314</span>    long sequence = -1L;<a name="line.314"></a>
+<span class="sourceLineNo">315</span>    if (this.ringBufferEventHandler != null) {<a name="line.315"></a>
+<span class="sourceLineNo">316</span>      // Get sequence first to avoid dead lock when ring buffer is full<a name="line.316"></a>
+<span class="sourceLineNo">317</span>      // Considering below sequence<a name="line.317"></a>
+<span class="sourceLineNo">318</span>      // 1. replaceWriter is called and zigzagLatch is initialized<a name="line.318"></a>
+<span class="sourceLineNo">319</span>      // 2. ringBufferEventHandler#onEvent is called and arrives at #attainSafePoint(long) then wait<a name="line.319"></a>
+<span class="sourceLineNo">320</span>      // on safePointReleasedLatch<a name="line.320"></a>
+<span class="sourceLineNo">321</span>      // 3. Since ring buffer is full, if we get sequence when publish sync, the replaceWriter<a name="line.321"></a>
+<span class="sourceLineNo">322</span>      // thread will wait for the ring buffer to be consumed, but the only consumer is waiting<a name="line.322"></a>
+<span class="sourceLineNo">323</span>      // replaceWriter thread to release safePointReleasedLatch, which causes a deadlock<a name="line.323"></a>
+<span class="sourceLineNo">324</span>      sequence = getSequenceOnRingBuffer();<a name="line.324"></a>
+<span class="sourceLineNo">325</span>      zigzagLatch = this.ringBufferEventHandler.attainSafePoint();<a name="line.325"></a>
+<span class="sourceLineNo">326</span>    }<a name="line.326"></a>
+<span class="sourceLineNo">327</span>    afterCreatingZigZagLatch();<a name="line.327"></a>
+<span class="sourceLineNo">328</span>    try {<a name="line.328"></a>
+<span class="sourceLineNo">329</span>      // Wait on the safe point to be achieved. Send in a sync in case nothing has hit the<a name="line.329"></a>
+<span class="sourceLineNo">330</span>      // ring buffer between the above notification of writer that we want it to go to<a name="line.330"></a>
+<span class="sourceLineNo">331</span>      // 'safe point' and then here where we are waiting on it to attain safe point. Use<a name="line.331"></a>
+<span class="sourceLineNo">332</span>      // 'sendSync' instead of 'sync' because we do not want this thread to block waiting on it<a name="line.332"></a>
+<span class="sourceLineNo">333</span>      // to come back. Cleanup this syncFuture down below after we are ready to run again.<a name="line.333"></a>
+<span class="sourceLineNo">334</span>      try {<a name="line.334"></a>
+<span class="sourceLineNo">335</span>        if (zigzagLatch != null) {<a name="line.335"></a>
+<span class="sourceLineNo">336</span>          // use assert to make sure no change breaks the logic that<a name="line.336"></a>
+<span class="sourceLineNo">337</span>          // sequence and zigzagLatch will be set together<a name="line.337"></a>
+<span class="sourceLineNo">338</span>          assert sequence &gt; 0L : "Failed to get sequence from ring buffer";<a name="line.338"></a>
+<span class="sourceLineNo">339</span>          TraceUtil.addTimelineAnnotation("awaiting safepoint");<a name="line.339"></a>
+<span class="sourceLineNo">340</span>          syncFuture = zigzagLatch.waitSafePoint(publishSyncOnRingBuffer(sequence, false));<a name="line.340"></a>
 <span class="sourceLineNo">341</span>        }<a name="line.341"></a>
-<span class="sourceLineNo">342</span>        LOG.warn(<a name="line.342"></a>
-<span class="sourceLineNo">343</span>          "Failed sync-before-close but no outstanding appends; closing WAL" + e.getMessage());<a name="line.343"></a>
-<span class="sourceLineNo">344</span>      }<a name="line.344"></a>
-<span class="sourceLineNo">345</span>      long oldFileLen = 0L;<a name="line.345"></a>
-<span class="sourceLineNo">346</span>      // It is at the safe point. Swap out writer from under the blocked writer thread.<a name="line.346"></a>
-<span class="sourceLineNo">347</span>      // TODO: This is close is inline with critical section. Should happen in background?<a name="line.347"></a>
-<span class="sourceLineNo">348</span>      if (this.writer != null) {<a name="line.348"></a>
-<span class="sourceLineNo">349</span>        oldFileLen = this.writer.getLength();<a name="line.349"></a>
-<span class="sourceLineNo">350</span>        try {<a name="line.350"></a>
-<span class="sourceLineNo">351</span>          TraceUtil.addTimelineAnnotation("closing writer");<a name="line.351"></a>
-<span class="sourceLineNo">352</span>          this.writer.close();<a name="line.352"></a>
-<span class="sourceLineNo">353</span>          TraceUtil.addTimelineAnnotation("writer closed");<a name="line.353"></a>
-<span class="sourceLineNo">354</span>          this.closeErrorCount.set(0);<a name="line.354"></a>
-<span class="sourceLineNo">355</span>        } catch (IOException ioe) {<a name="line.355"></a>
-<span class="sourceLineNo">356</span>          int errors = closeErrorCount.incrementAndGet();<a name="line.356"></a>
-<span class="sourceLineNo">357</span>          if (!isUnflushedEntries() &amp;&amp; (errors &lt;= this.closeErrorsTolerated)) {<a name="line.357"></a>
-<span class="sourceLineNo">358</span>            LOG.warn("Riding over failed WAL close of " + oldPath + ", cause=\"" + ioe.getMessage()<a name="line.358"></a>
-<span class="sourceLineNo">359</span>                + "\", errors=" + errors<a name="line.359"></a>
-<span class="sourceLineNo">360</span>                + "; THIS FILE WAS NOT CLOSED BUT ALL EDITS SYNCED SO SHOULD BE OK");<a name="line.360"></a>
-<span class="sourceLineNo">361</span>          } else {<a name="line.361"></a>
-<span class="sourceLineNo">362</span>            throw ioe;<a name="line.362"></a>
-<span class="sourceLineNo">363</span>          }<a name="line.363"></a>
-<span class="sourceLineNo">364</span>        }<a name="line.364"></a>
-<span class="sourceLineNo">365</span>      }<a name="line.365"></a>
-<span class="sourceLineNo">366</span>      logRollAndSetupWalProps(oldPath, newPath, oldFileLen);<a name="line.366"></a>
-<span class="sourceLineNo">367</span>      this.writer = nextWriter;<a name="line.367"></a>
-<span class="sourceLineNo">368</span>      if (nextWriter != null &amp;&amp; nextWriter instanceof ProtobufLogWriter) {<a name="line.368"></a>
-<span class="sourceLineNo">369</span>        this.hdfs_out = ((ProtobufLogWriter) nextWriter).getStream();<a name="line.369"></a>
-<span class="sourceLineNo">370</span>      } else {<a name="line.370"></a>
-<span class="sourceLineNo">371</span>        this.hdfs_out = null;<a name="line.371"></a>
-<span class="sourceLineNo">372</span>      }<a name="line.372"></a>
-<span class="sourceLineNo">373</span>    } catch (InterruptedException ie) {<a name="line.373"></a>
-<span class="sourceLineNo">374</span>      // Perpetuate the interrupt<a name="line.374"></a>
-<span class="sourceLineNo">375</span>      Thread.currentThread().interrupt();<a name="line.375"></a>
-<span class="sourceLineNo">376</span>    } catch (IOException e) {<a name="line.376"></a>
-<span class="sourceLineNo">377</span>      long count = getUnflushedEntriesCount();<a name="line.377"></a>
-<span class="sourceLineNo">378</span>      LOG.error("Failed close of WAL writer " + oldPath + ", unflushedEntries=" + count, e);<a name="line.378"></a>
-<span class="sourceLineNo">379</span>      throw new FailedLogCloseException(oldPath + ", unflushedEntries=" + count, e);<a name="line.379"></a>
-<span class="sourceLineNo">380</span>    } finally {<a name="line.380"></a>
-<span class="sourceLineNo">381</span>      // Let the writer thread go regardless, whether error or not.<a name="line.381"></a>
-<span class="sourceLineNo">382</span>      if (zigzagLatch != null) {<a name="line.382"></a>
-<span class="sourceLineNo">383</span>        zigzagLatch.releaseSafePoint();<a name="line.383"></a>
-<span class="sourceLineNo">384</span>        // syncFuture will be null if we failed our wait on safe point above. Otherwise, if<a name="line.384"></a>
-<span class="sourceLineNo">385</span>        // latch was obtained successfully, the sync we threw in either trigger the latch or it<a name="line.385"></a>
-<span class="sourceLineNo">386</span>        // got stamped with an exception because the WAL was damaged and we could not sync. Now<a name="line.386"></a>
-<span class="sourceLineNo">387</span>        // the write pipeline has been opened up again by releasing the safe point, process the<a name="line.387"></a>
-<span class="sourceLineNo">388</span>        // syncFuture we got above. This is probably a noop but it may be stale exception from<a name="line.388"></a>
-<span class="sourceLineNo">389</span>        // when old WAL was in place. Catch it if so.<a name="line.389"></a>
-<span class="sourceLineNo">390</span>        if (syncFuture != null) {<a name="line.390"></a>
-<span class="sourceLineNo">391</span>          try {<a name="line.391"></a>
-<span class="sourceLineNo">392</span>            blockOnSync(syncFuture);<a name="line.392"></a>
-<span class="sourceLineNo">393</span>          } catch (IOException ioe) {<a name="line.393"></a>
-<span class="sourceLineNo">394</span>            if (LOG.isTraceEnabled()) {<a name="line.394"></a>
-<span class="sourceLineNo">395</span>              LOG.trace("Stale sync exception", ioe);<a name="line.395"></a>
-<span class="sourceLineNo">396</span>            }<a name="line.396"></a>
-<span class="sourceLineNo">397</span>          }<a name="line.397"></a>
-<span class="sourceLineNo">398</span>        }<a name="line.398"></a>
-<span class="sourceLineNo">399</span>      }<a name="line.399"></a>
-<span class="sourceLineNo">400</span>    }<a name="line.400"></a>
-<span class="sourceLineNo">401</span>  }<a name="line.401"></a>
-<span class="sourceLineNo">402</span><a name="line.402"></a>
-<span class="sourceLineNo">403</span>  @Override<a name="line.403"></a>
-<span class="sourceLineNo">404</span>  protected void doShutdown() throws IOException {<a name="line.404"></a>
-<span class="sourceLineNo">405</span>    // Shutdown the disruptor. Will stop after all entries have been processed. Make sure we<a name="line.405"></a>
-<span class="sourceLineNo">406</span>    // have stopped incoming appends before calling this else it will not shutdown. We are<a name="line.406"></a>
-<span class="sourceLineNo">407</span>    // conservative below waiting a long time and if not elapsed, then halting.<a name="line.407"></a>
-<span class="sourceLineNo">408</span>    if (this.disruptor != null) {<a name="line.408"></a>
-<span class="sourceLineNo">409</span>      long timeoutms = conf.getLong("hbase.wal.disruptor.shutdown.timeout.ms", 60000);<a name="line.409"></a>
-<span class="sourceLineNo">410</span>      try {<a name="line.410"></a>
-<span class="sourceLineNo">411</span>        this.disruptor.shutdown(timeoutms, TimeUnit.MILLISECONDS);<a name="line.411"></a>
-<span class="sourceLineNo">412</span>      } catch (TimeoutException e) {<a name="line.412"></a>
-<span class="sourceLineNo">413</span>        LOG.warn("Timed out bringing down disruptor after " + timeoutms + "ms; forcing halt "<a name="line.413"></a>
-<span class="sourceLineNo">414</span>            + "(It is a problem if this is NOT an ABORT! -- DATALOSS!!!!)");<a name="line.414"></a>
-<span class="sourceLineNo">415</span>        this.disruptor.halt();<a name="line.415"></a>
-<span class="sourceLineNo">416</span>        this.disruptor.shutdown();<a name="line.416"></a>
-<span class="sourceLineNo">417</span>      }<a name="line.417"></a>
-<span class="sourceLineNo">418</span>    }<a name="line.418"></a>
-<span class="sourceLineNo">419</span><a name="line.419"></a>
-<span class="sourceLineNo">420</span>    if (LOG.isDebugEnabled()) {<a name="line.420"></a>
-<span class="sourceLineNo">421</span>      LOG.debug("Closing WAL writer in " + FSUtils.getPath(walDir));<a name="line.421"></a>
-<span class="sourceLineNo">422</span>    }<a name="line.422"></a>
-<span class="sourceLineNo">423</span>    if (this.writer != null) {<a name="line.423"></a>
-<span class="sourceLineNo">424</span>      this.writer.close();<a name="line.424"></a>
-<span class="sourceLineNo">425</span>      this.writer = null;<a name="line.425"></a>
-<span class="sourceLineNo">426</span>    }<a name="line.426"></a>
-<span class="sourceLineNo">427</span>  }<a name="line.427"></a>
-<span class="sourceLineNo">428</span><a name="line.428"></a>
-<span class="sourceLineNo">429</span>  @edu.umd.cs.findbugs.annotations.SuppressWarnings(value = "NP_NULL_ON_SOME_PATH_EXCEPTION",<a name="line.429"></a>
-<span class="sourceLineNo">430</span>      justification = "Will never be null")<a name="line.430"></a>
-<span class="sourceLineNo">431</span>  @Override<a name="line.431"></a>
-<span class="sourceLineNo">432</span>  public long append(final RegionInfo hri, final WALKeyImpl key, final WALEdit edits,<a name="line.432"></a>
-<span class="sourceLineNo">433</span>      final boolean inMemstore) throws IOException {<a name="line.433"></a>
-<span class="sourceLineNo">434</span>    return stampSequenceIdAndPublishToRingBuffer(hri, key, edits, inMemstore,<a name="line.434"></a>
-<span class="sourceLineNo">435</span>      disruptor.getRingBuffer());<a name="line.435"></a>
-<span class="sourceLineNo">436</span>  }<a name="line.436"></a>
-<span class="sourceLineNo">437</span><a name="line.437"></a>
-<span class="sourceLineNo">438</span>  /**<a name="line.438"></a>
-<span class="sourceLineNo">439</span>   * Thread to runs the hdfs sync call. This call takes a while to complete. This is the longest<a name="line.439"></a>
-<span class="sourceLineNo">440</span>   * pole adding edits to the WAL and this must complete to be sure all edits persisted. We run<a name="line.440"></a>
-<span class="sourceLineNo">441</span>   * multiple threads sync'ng rather than one that just syncs in series so we have better latencies;<a name="line.441"></a>
-<span class="sourceLineNo">442</span>   * otherwise, an edit that arrived just after a sync started, might have to wait almost the length<a name="line.442"></a>
-<span class="sourceLineNo">443</span>   * of two sync invocations before it is marked done.<a name="line.443"></a>
-<span class="sourceLineNo">444</span>   * &lt;p&gt;<a name="line.444"></a>
-<span class="sourceLineNo">445</span>   * When the sync completes, it marks all the passed in futures done. On the other end of the sync<a name="line.445"></a>
-<span class="sourceLineNo">446</span>   * future is a blocked thread, usually a regionserver Handler. There may be more than one future<a name="line.446"></a>
-<span class="sourceLineNo">447</span>   * passed in the case where a few threads arrive at about the same time and all invoke 'sync'. In<a name="line.447"></a>
-<span class="sourceLineNo">448</span>   * this case we'll batch up the invocations and run one filesystem sync only for a batch of<a name="line.448"></a>
-<span class="sourceLineNo">449</span>   * Handler sync invocations. Do not confuse these Handler SyncFutures with the futures an<a name="line.449"></a>
-<span class="sourceLineNo">450</span>   * ExecutorService returns when you call submit. We have no use for these in this model. These<a name="line.450"></a>
-<span class="sourceLineNo">451</span>   * SyncFutures are 'artificial', something to hold the Handler until the filesystem sync<a name="line.451"></a>
-<span class="sourceLineNo">452</span>   * completes.<a name="line.452"></a>
-<span class="sourceLineNo">453</span>   */<a name="line.453"></a>
-<span class="sourceLineNo">454</span>  private class SyncRunner extends HasThread {<a name="line.454"></a>
-<span class="sourceLineNo">455</span>    private volatile long sequence;<a name="line.455"></a>
-<span class="sourceLineNo">456</span>    // Keep around last exception thrown. Clear on successful sync.<a name="line.456"></a>
-<span class="sourceLineNo">457</span>    private final BlockingQueue&lt;SyncFuture&gt; syncFutures;<a name="line.457"></a>
-<span class="sourceLineNo">458</span>    private volatile SyncFuture takeSyncFuture = null;<a name="line.458"></a>
-<span class="sourceLineNo">459</span><a name="line.459"></a>
-<span class="sourceLineNo">460</span>    SyncRunner(final String name, final int maxHandlersCount) {<a name="line.460"></a>
-<span class="sourceLineNo">461</span>      super(name);<a name="line.461"></a>
-<span class="sourceLineNo">462</span>      // LinkedBlockingQueue because of<a name="line.462"></a>
-<span class="sourceLineNo">463</span>      // http://www.javacodegeeks.com/2010/09/java-best-practices-queue-battle-and.html<a name="line.463"></a>
-<span class="sourceLineNo">464</span>      // Could use other blockingqueues here or concurrent queues.<a name="line.464"></a>
-<span class="sourceLineNo">465</span>      //<a name="line.465"></a>
-<span class="sourceLineNo">466</span>      // We could let the capacity be 'open' but bound it so we get alerted in pathological case<a name="line.466"></a>
-<span class="sourceLineNo">467</span>      // where we cannot sync and we have a bunch of threads all backed up waiting on their syncs<a name="line.467"></a>
-<span class="sourceLineNo">468</span>      // to come in. LinkedBlockingQueue actually shrinks when you remove elements so Q should<a name="line.468"></a>
-<span class="sourceLineNo">469</span>      // stay neat and tidy in usual case. Let the max size be three times the maximum handlers.<a name="line.469"></a>
-<span class="sourceLineNo">470</span>      // The passed in maxHandlerCount is the user-level handlers which is what we put up most of<a name="line.470"></a>
-<span class="sourceLineNo">471</span>      // but HBase has other handlers running too -- opening region handlers which want to write<a name="line.471"></a>
-<span class="sourceLineNo">472</span>      // the meta table when succesful (i.e. sync), closing handlers -- etc. These are usually<a name="line.472"></a>
-<span class="sourceLineNo">473</span>      // much fewer in number than the user-space handlers so Q-size should be user handlers plus<a name="line.473"></a>
-<span class="sourceLineNo">474</span>      // some space for these other handlers. Lets multiply by 3 for good-measure.<a name="line.474"></a>
-<span class="sourceLineNo">475</span>      this.syncFutures = new LinkedBlockingQueue&lt;&gt;(maxHandlersCount * 3);<a name="line.475"></a>
-<span class="sourceLineNo">476</span>    }<a name="line.476"></a>
-<span class="sourceLineNo">477</span><a name="line.477"></a>
-<span class="sourceLineNo">478</span>    void offer(final long sequence, final SyncFuture[] syncFutures, final int syncFutureCount) {<a name="line.478"></a>
-<span class="sourceLineNo">479</span>      // Set sequence first because the add to the queue will wake the thread if sleeping.<a name="line.479"></a>
-<span class="sourceLineNo">480</span>      this.sequence = sequence;<a name="line.480"></a>
-<span class="sourceLineNo">481</span>      for (int i = 0; i &lt; syncFutureCount; ++i) {<a name="line.481"></a>
-<span class="sourceLineNo">482</span>        this.syncFutures.add(syncFutures[i]);<a name="line.482"></a>
-<span class="sourceLineNo">483</span>      }<a name="line.483"></a>
-<span class="sourceLineNo">484</span>    }<a name="line.484"></a>
-<span class="sourceLineNo">485</span><a name="line.485"></a>
-<span class="sourceLineNo">486</span>    /**<a name="line.486"></a>
-<span class="sourceLineNo">487</span>     * Release the passed &lt;code&gt;syncFuture&lt;/code&gt;<a name="line.487"></a>
-<span class="sourceLineNo">488</span>     * @return Returns 1.<a name="line.488"></a>
-<span class="sourceLineNo">489</span>     */<a name="line.489"></a>
-<span class="sourceLineNo">490</span>    private int releaseSyncFuture(final SyncFuture syncFuture, final long currentSequence,<a name="line.490"></a>
-<span class="sourceLineNo">491</span>        final Throwable t) {<a name="line.491"></a>
-<span class="sourceLineNo">492</span>      if (!syncFuture.done(currentSequence, t)) {<a name="line.492"></a>
-<span class="sourceLineNo">493</span>        throw new IllegalStateException();<a name="line.493"></a>
-<span class="sourceLineNo">494</span>      }<a name="line.494"></a>
-<span class="sourceLineNo">495</span><a name="line.495"></a>
-<span class="sourceLineNo">496</span>      // This function releases one sync future only.<a name="line.496"></a>
-<span class="sourceLineNo">497</span>      return 1;<a name="line.497"></a>
-<span class="sourceLineNo">498</span>    }<a name="line.498"></a>
-<span class="sourceLineNo">499</span><a name="line.499"></a>
-<span class="sourceLineNo">500</span>    /**<a name="line.500"></a>
-<span class="sourceLineNo">501</span>     * Release all SyncFutures whose sequence is &lt;= &lt;code&gt;currentSequence&lt;/code&gt;.<a name="line.501"></a>
-<span class="sourceLineNo">502</span>     * @param t May be non-null if we are processing SyncFutures because an exception was thrown.<a name="line.502"></a>
-<span class="sourceLineNo">503</span>     * @return Count of SyncFutures we let go.<a name="line.503"></a>
-<span class="sourceLineNo">504</span>     */<a name="line.504"></a>
-<span class="sourceLineNo">505</span>    private int releaseSyncFutures(final long currentSequence, final Throwable t) {<a name="line.505"></a>
-<span class="sourceLineNo">506</span>      int syncCount = 0;<a name="line.506"></a>
-<span class="sourceLineNo">507</span>      for (SyncFuture syncFuture; (syncFuture = this.syncFutures.peek()) != null;) {<a name="line.507"></a>
-<span class="sourceLineNo">508</span>        if (syncFuture.getTxid() &gt; currentSequence) {<a name="line.508"></a>
-<span class="sourceLineNo">509</span>          break;<a name="line.509"></a>
-<span class="sourceLineNo">510</span>        }<a name="line.510"></a>
-<span class="sourceLineNo">511</span>        releaseSyncFuture(syncFuture, currentSequence, t);<a name="line.511"></a>
-<span class="sourceLineNo">512</span>        if (!this.syncFutures.remove(syncFuture)) {<a name="line.512"></a>
-<span class="sourceLineNo">513</span>          throw new IllegalStateException(syncFuture.toString());<a name="line.513"></a>
-<span class="sourceLineNo">514</span>        }<a name="line.514"></a>
-<span class="sourceLineNo">515</span>        syncCount++;<a name="line.515"></a>
-<span class="sourceLineNo">516</span>      }<a name="line.516"></a>
-<span class="sourceLineNo">517</span>      return syncCount;<a name="line.517"></a>
-<span class="sourceLineNo">518</span>    }<a name="line.518"></a>
-<span class="sourceLineNo">519</span><a name="line.519"></a>
-<span class="sourceLineNo">520</span>    /**<a name="line.520"></a>
-<span class="sourceLineNo">521</span>     * @param sequence The sequence we ran the filesystem sync against.<a name="line.521"></a>
-<span class="sourceLineNo">522</span>     * @return Current highest synced sequence.<a name="line.522"></a>
-<span class="sourceLineNo">523</span>     */<a name="line.523"></a>
-<span class="sourceLineNo">524</span>    private long updateHighestSyncedSequence(long sequence) {<a name="line.524"></a>
-<span class="sourceLineNo">525</span>      long currentHighestSyncedSequence;<a name="line.525"></a>
-<span class="sourceLineNo">526</span>      // Set the highestSyncedSequence IFF our current sequence id is the 'highest'.<a name="line.526"></a>
-<span class="sourceLineNo">527</span>      do {<a name="line.527"></a>
-<span class="sourceLineNo">528</span>        currentHighestSyncedSequence = highestSyncedTxid.get();<a name="line.528"></a>
-<span class="sourceLineNo">529</span>        if (currentHighestSyncedSequence &gt;= sequence) {<a name="line.529"></a>
-<span class="sourceLineNo">530</span>          // Set the sync number to current highwater mark; might be able to let go more<a name="line.530"></a>
-<span class="sourceLineNo">531</span>          // queued sync futures<a name="line.531"></a>
-<span class="sourceLineNo">532</span>          sequence = currentHighestSyncedSequence;<a name="line.532"></a>
-<span class="sourceLineNo">533</span>          break;<a name="line.533"></a>
-<span class="sourceLineNo">534</span>        }<a name="line.534"></a>
-<span class="sourceLineNo">535</span>      } while (!highestSyncedTxid.compareAndSet(currentHighestSyncedSequence, sequence));<a name="line.535"></a>
-<span class="sourceLineNo">536</span>      return sequence;<a name="line.536"></a>
-<span class="sourceLineNo">537</span>    }<a name="line.537"></a>
-<span class="sourceLineNo">538</span><a name="line.538"></a>
-<span class="sourceLineNo">539</span>    boolean areSyncFuturesReleased() {<a name="line.539"></a>
-<span class="sourceLineNo">540</span>      // check whether there is no sync futures offered, and no in-flight sync futures that is being<a name="line.540"></a>
-<span class="sourceLineNo">541</span>      // processed.<a name="line.541"></a>
-<span class="sourceLineNo">542</span>      return syncFutures.size() &lt;= 0<a name="line.542"></a>
-<span class="sourceLineNo">543</span>          &amp;&amp; takeSyncFuture == null;<a name="line.543"></a>
-<span class="sourceLineNo">544</span>    }<a name="line.544"></a>
-<span class="sourceLineNo">545</span><a name="line.545"></a>
-<span class="sourceLineNo">546</span>    @Override<a name="line.546"></a>
-<span class="sourceLineNo">547</span>    public void run() {<a name="line.547"></a>
-<span class="sourceLineNo">548</span>      long currentSequence;<a name="line.548"></a>
-<span class="sourceLineNo">549</span>      while (!isInterrupted()) {<a name="line.549"></a>
-<span class="sourceLineNo">550</span>        int syncCount = 0;<a name="line.550"></a>
-<span class="sourceLineNo">551</span><a name="line.551"></a>
-<span class="sourceLineNo">552</span>        try {<a name="line.552"></a>
-<span class="sourceLineNo">553</span>          while (true) {<a name="line.553"></a>
-<span class="sourceLineNo">554</span>            takeSyncFuture = null;<a name="line.554"></a>
-<span class="sourceLineNo">555</span>            // We have to process what we 'take' from the queue<a name="line.555"></a>
-<span class="sourceLineNo">556</span>            takeSyncFuture = this.syncFutures.take();<a name="line.556"></a>
-<span class="sourceLineNo">557</span>            currentSequence = this.sequence;<a name="line.557"></a>
-<span class="sourceLineNo">558</span>            long syncFutureSequence = takeSyncFuture.getTxid();<a name="line.558"></a>
-<span class="sourceLineNo">559</span>            if (syncFutureSequence &gt; currentSequence) {<a name="line.559"></a>
-<span class="sourceLineNo">560</span>              throw new IllegalStateException("currentSequence=" + currentSequence<a name="line.560"></a>
-<span class="sourceLineNo">561</span>                  + ", syncFutureSequence=" + syncFutureSequence);<a name="line.561"></a>
-<span class="sourceLineNo">562</span>            }<a name="line.562"></a>
-<span class="sourceLineNo">563</span>            // See if we can process any syncfutures BEFORE we go sync.<a name="line.563"></a>
-<span class="sourceLineNo">564</span>            long currentHighestSyncedSequence = highestSyncedTxid.get();<a name="line.564"></a>
-<span class="sourceLineNo">565</span>            if (currentSequence &l

<TRUNCATED>