GitHub user mohammadshahidkhan opened a pull request:
https://github.com/apache/incubator-carbondata/pull/77
CARBONDATA-153 Record count is not matching while loading the data when one
data node went down in HA setup
Record count is not matching while loading the data when one data node went
down in HA setup
As per previous implementation :
Scenario:
No. of Running executors = 3
No. Data Nodes = 2
Total Unique blocks = 96
Then as per the previous implementation no. of blocks per node = 32.
While assigning blocks only 66 blocks getting allocated amongs two
execuotors.
Third executor is not getting any blocks since we are considering only node
local allocation.
Solution:
// so now we have a map of node vs blocks. allocate the block as per the
order
createOutputMap(nodeBlocksMap, blocksPerNode, uniqueBlocks,
nodeAndBlockMapping, activeNodes);
After doing node block mapping we will map the remaining activeNodes in the
nodeBlocksMap in the assignLeftOverBlocks so that assignLeftOverBlocks can
take care the assignment of remaining blocks.
// if any blocks remain then assign them to nodes in round robin.
assignLeftOverBlocks(nodeBlocksMap, uniqueBlocks, blocksPerNode);
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mohammadshahidkhan/incubator-carbondata
fixed_block_distribution_when_active_node_grt_node_nodehaving_data
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-carbondata/pull/77.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #77
----
commit e0fe3491d1750d586efde882d3a9882d325954a1
Author: mohammadshahidkhan <[email protected]>
Date: 2016-08-09T05:17:02Z
CARBONDATA-153 Record count is not matching while loading the data when one
data node went down in HA setup
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
