>1. >Why does "HBase replication" need replicationSink? >I think replicationSource can do replicationSink's work as well. >And if we don't use replicationSink, we just need one time I/O.
ReplicationSink used to apply all HLog edits to peer cluster. If we remove ReplicationSink from current architecture, so how to send data to peer cluster? Using API "HTableInterface#put"? So there's no difference between replication write requests and normal user write requests. One potential problem is that the replication write request may occupy all the handler threads on RegionServer, then affect normal user write requests. >2. >The queue added HLog path in replicationSource is PriorityBlockingQueue. >If the queue is full, HLog path cannot be added to the queue. >How to deal with the situation? We didn't limit the maximum size of that queue, right? Jieshan. ________________________________________ From: Cliff [[email protected]] Sent: Saturday, November 22, 2014 12:32 PM To: [email protected] Subject: Questions about HBase replication 1. Why does "HBase replication" need replicationSink? I think replicationSource can do replicationSink's work as well. And if we don't use replicationSink, we just need one time I/O. 2. The queue added HLog path in replicationSource is PriorityBlockingQueue. If the queue is full, HLog path cannot be added to the queue. How to deal with the situation? -- View this message in context: http://apache-hbase.679495.n3.nabble.com/Questions-about-HBase-replication-tp4066266.html Sent from the HBase Developer mailing list archive at Nabble.com.
