You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Lei Sun (JIRA)" <ji...@apache.org> on 2017/08/15 16:55:00 UTC
[jira] [Comment Edited] (GOBBLIN-205) Fix Replication bug in Push
Mode
[ https://issues.apache.org/jira/browse/GOBBLIN-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127519#comment-16127519 ]
Lei Sun edited comment on GOBBLIN-205 at 8/15/17 4:54 PM:
----------------------------------------------------------
The issue is, replication in Push-Mode doesn't generate workunits.
Recall that in the push mode, the source is the {{EndPoint}} that runs the distcp job. The bug is in {{ConfigBasedMultiDatasets.java}}, in the iteration of line 130: If current {{pushCandidate}} is not the {{EndPoint}} that is running the push job, we should continue to iterate the list of {{pushCandidate}} instead of return immediately.
was (Author: lesun):
The issue is, replication in Push-Mode doesn't generate workunits.
Recall that in the push mode, the source is the `EndPoint` that runs the distcp job. The bug is in `ConfigBasedMultiDatasets.java`, in the iteration of line 130: If current `pushCandidate` is not the `EndPoint` that is running the push job, we should continue to iterate the list of `pushCandidate` instead of return immediately.
> Fix Replication bug in Push Mode
> --------------------------------
>
> Key: GOBBLIN-205
> URL: https://issues.apache.org/jira/browse/GOBBLIN-205
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Lei Sun
> Assignee: Lei Sun
>
> Fix bugs In DistcpNG (Gobblin/copy) in terms of EndPoint comparison.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)