S2S Provenance - Destination penalized
I'm trying to use SiteToSiteProvenanceReportingTask and I have set it up like this:
The destination instance contains only a flow with a FromKDE input port.
However I'm getting the following error:
SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] Error running task SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] due to org.apache.nifi.processor.exception.ProcessException: All destination nodes are penalized; will attempt to send data later
Help, please?
apache-nifi
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
add a comment |
I'm trying to use SiteToSiteProvenanceReportingTask and I have set it up like this:
The destination instance contains only a flow with a FromKDE input port.
However I'm getting the following error:
SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] Error running task SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] due to org.apache.nifi.processor.exception.ProcessException: All destination nodes are penalized; will attempt to send data later
Help, please?
apache-nifi
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
add a comment |
I'm trying to use SiteToSiteProvenanceReportingTask and I have set it up like this:
The destination instance contains only a flow with a FromKDE input port.
However I'm getting the following error:
SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] Error running task SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] due to org.apache.nifi.processor.exception.ProcessException: All destination nodes are penalized; will attempt to send data later
Help, please?
apache-nifi
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
I'm trying to use SiteToSiteProvenanceReportingTask and I have set it up like this:
The destination instance contains only a flow with a FromKDE input port.
However I'm getting the following error:
SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] Error running task SiteToSiteProvenanceReportingTask[id=f6256705-0167-1000-c0ea-0843f4a65948] due to org.apache.nifi.processor.exception.ProcessException: All destination nodes are penalized; will attempt to send data later
Help, please?
apache-nifi
apache-nifi
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
asked Dec 28 '18 at 19:24
Vinicius Zolin De JesusVinicius Zolin De Jesus
757
757
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If the destination has no component (processor/PG) which can perform work on the incoming flowfiles, it penalizes the incoming connection to discourage it from sending more. If you are trying to debug, add a LogAttribute processor to simply process the flowfiles and the error should go away.
If the destination does have components, examine those to see if any are throwing exceptions and penalizing the incoming flowfiles. Resolve these errors to allow the flow to resume.
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
The destination has several components, however none of them are throwing any exceptions
– Vinicius Zolin De Jesus
Jan 2 at 18:39
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53963386%2fs2s-provenance-destination-penalized%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If the destination has no component (processor/PG) which can perform work on the incoming flowfiles, it penalizes the incoming connection to discourage it from sending more. If you are trying to debug, add a LogAttribute processor to simply process the flowfiles and the error should go away.
If the destination does have components, examine those to see if any are throwing exceptions and penalizing the incoming flowfiles. Resolve these errors to allow the flow to resume.
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
The destination has several components, however none of them are throwing any exceptions
– Vinicius Zolin De Jesus
Jan 2 at 18:39
add a comment |
If the destination has no component (processor/PG) which can perform work on the incoming flowfiles, it penalizes the incoming connection to discourage it from sending more. If you are trying to debug, add a LogAttribute processor to simply process the flowfiles and the error should go away.
If the destination does have components, examine those to see if any are throwing exceptions and penalizing the incoming flowfiles. Resolve these errors to allow the flow to resume.
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
The destination has several components, however none of them are throwing any exceptions
– Vinicius Zolin De Jesus
Jan 2 at 18:39
add a comment |
If the destination has no component (processor/PG) which can perform work on the incoming flowfiles, it penalizes the incoming connection to discourage it from sending more. If you are trying to debug, add a LogAttribute processor to simply process the flowfiles and the error should go away.
If the destination does have components, examine those to see if any are throwing exceptions and penalizing the incoming flowfiles. Resolve these errors to allow the flow to resume.
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
If the destination has no component (processor/PG) which can perform work on the incoming flowfiles, it penalizes the incoming connection to discourage it from sending more. If you are trying to debug, add a LogAttribute processor to simply process the flowfiles and the error should go away.
If the destination does have components, examine those to see if any are throwing exceptions and penalizing the incoming flowfiles. Resolve these errors to allow the flow to resume.
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
answered Dec 31 '18 at 18:30
AndyAndy
7,75012145
7,75012145
The destination has several components, however none of them are throwing any exceptions
– Vinicius Zolin De Jesus
Jan 2 at 18:39
add a comment |
The destination has several components, however none of them are throwing any exceptions
– Vinicius Zolin De Jesus
Jan 2 at 18:39
The destination has several components, however none of them are throwing any exceptions
– Vinicius Zolin De Jesus
Jan 2 at 18:39
The destination has several components, however none of them are throwing any exceptions
– Vinicius Zolin De Jesus
Jan 2 at 18:39
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53963386%2fs2s-provenance-destination-penalized%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
