Hi Joe, I haven't encountered that issue. Would you tell us more details? So that we can investigate it.
1. Which transport protocol are you using? RAW or HTTP 2. Is this a pull or push transfer? Pull = client NiFi pulls from remote OutputPort, Push = sends to remote InputPort 3. Is compression enabled? 4. How many ports are configured? If there are more than one, RPG indicates that it's 'Transmitting' as long as at least one port is transmitting, while others can be disabled. Right click a RPG then select 'Remote Ports' to see each port status. 5. How often does it happen? Stops once per hour/day/week?? 6. Please share your environment, OS, Java version ... etc 7. If possible, please take stack-trace while you are facing that issue, and share it with us, by running: "$NIFI_HOME/bin/nifh.sh dump" stack-trace will be written to nifi-bootstrap.log 8. Is proxy used? Thanks, Koji On Thu, Jun 15, 2017 at 12:41 AM, Joe Gresock <[email protected]> wrote: > Before I investigate further, has anyone encountered NiFi RPGs "disabling" > after a while in 1.3.0? Their status is reported as enabled/transmitting, > but the flow files just sit there until I "enable transmission" again. > This happens for nearly all of the RPGs I have in my flow. I just have to > keep "kick starting" them periodically to keep things flowing. > > This behavior did not happen in 1.2.0. > -- > I know what it is to be in need, and I know what it is to have plenty. I > have learned the secret of being content in any and every situation, > whether well fed or hungry, whether living in plenty or in want. I can do > all this through him who gives me strength. *-Philippians 4:12-13*
