[
https://issues.apache.org/jira/browse/NIFI-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563850#comment-16563850
]
vivek bombatkar commented on NIFI-4537:
---------------------------------------
The default option for 'Ignore STDIN' is false. Not sure why you mention to
change it to default!
We face same annoying problem while doing spark2-submit from
ExecuteStreamCommand.
We have 'Ignore STDIN' is false.
We have 100s of flowfile waiting for execution (spark2-submit), but after 10-12
successful execution processor stop responding.
> ExecuteStreamCommand stuck, cannot play cannot run
> --------------------------------------------------
>
> Key: NIFI-4537
> URL: https://issues.apache.org/jira/browse/NIFI-4537
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: dav
> Priority: Major
> Attachments: executeStreamCommand.png
>
>
> At a certain time the ExecuteStreamCommand get stucked, but it seems to be in
> running state.
> When I stop the proccessor from the web UI the processor seems to be stopped
> but If I try to Put in RUNNING state the stucked processor, with Nifi API
> REST, i get this response:
> 2017-10-27 08:50:43,749 INFO [NiFi Web Server-96840]
> o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException:
> 015e1005-8820-176e-f509-ca592def60b0 cannot be started because it is not
> stopped. Current state is STOPPING. Returning Conflict response.
> I found a hortonworks question already open but no solution is given
> [https://community.hortonworks.com/questions/131434/scheduling-executestreamcommand-processor-with-gen.html?childToView=142637#answer-142637]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
