Local Index data not replicating for older HBase versions

2019-04-30 Thread Hieu Nguyen
Hi, We are on Phoenix 4.14-cdh5.11. We are experiencing an issue where local index data is not being replicated through HBase replication. As suggested in a previous email thread (

Re: Phoenix Mapreduce

2019-04-30 Thread Shawn Li
Got it, thanks for the clarification, Josh! On Tue, Apr 30, 2019, 10:34 AM Josh Elser wrote: > No, you will not "lose" data. You will just have mappers that read from > more than one Region (and thus, more than one RegionServer). The hope in > this approach is that we can launch Mappers on the

Re: Phoenix Mapreduce

2019-04-30 Thread Josh Elser
No, you will not "lose" data. You will just have mappers that read from more than one Region (and thus, more than one RegionServer). The hope in this approach is that we can launch Mappers on the same node of the RegionServer hosting your Region and avoid any reading any data over the network.

Phoenix Mapreduce

2019-04-30 Thread Shawn Li
Hi, The number of Map in Phoenix Mapreduce is determined by table region number. My question is: if the region is split due to other injection process while Phoenix Mapreduce job is running, do we lose reading some data due to this split? As now we have more regions than maps, and the maps only