Github user Jay357089 commented on the issue:
https://github.com/apache/incubator-carbondata/pull/457
@eason-lyx
### i verifeid in 6 nodes yarn cluster. after i killed
coarseGrainExecutorbacked in one node, then the task can be restarted in
another node. Process infomation is like below:
INFO 23-12 07:36:19,212 - Starting task 2.0 in stage 7.0 (TID 316,
linux-136, partition 2,NODE_LOCAL, 4240 bytes)
INFO 23-12 07:36:19,212 - Starting task 3.0 in stage 7.0 (TID 317,
linux-134, partition 3,NODE_LOCAL, 4240 bytes)
INFO 23-12 07:36:19,212 - Starting task 0.0 in stage 7.0 (TID 318,
linux-139, partition 0,NODE_LOCAL, 4240 bytes)
INFO 23-12 07:36:19,212 - Starting task 1.0 in stage 7.0 (TID 319,
linux-135, partition 1,NODE_LOCAL, 4274 bytes)
INFO 23-12 07:36:19,212 - Starting task 5.0 in stage 7.0 (TID 320,
linux-141, partition 5,NODE_LOCAL, 4233 bytes)
INFO 23-12 07:36:19,212 - Starting task 4.0 in stage 7.0 (TID 321,
linux-140, partition 4,NODE_LOCAL, 4233 bytes)
ERROR 23-12 07:37:48,021 - Lost executor 1 on linux-139: Container marked
as failed: container_1482169114977_0026_01_000002 on host: linux-139. Exit
status: 137. Diagnostics: Container killed on request. Exit code is 137
Container exited with a non-zero exit code 137
Killed by external signal
INFO 23-12 07:37:48,758 - Starting task 0.1 in stage 7.0 (TID 322,
linux-141, partition 0,RACK_LOCAL, 4240 bytes)
### and the amount of finally generated carbon data file is same with that
generated in normal process.
### so, i think it's okay to keep only one preferred location.
---
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.
---
