[DISCUSS] NIFI-1069 / PR1093 - Return code for a NiFi not responding to ping

I would say go with 4. Ansible will see 1, 2, 3, 4, 69 as not running and do the correct thing. Puppet sees 0 vs non zero. I think If he service is up running and responding to pings return 0 anything else should return another code. This will allow these tools to restart the application to get

Re: [DISCUSS] NIFI-1069 / PR1093 - Return code for a NiFi not responding to ping

Andre, In that case, I agree with you that a 4 would be the proper response. Things that I can think of that may cause it not to respond: 1) Long Garbage Collection pause 2) Stuck in some sort of infinite loop or just way overtaxed CPU 3) Too many open files prevents it from accepting the

[DISCUSS] NIFI-1069 / PR1093 - Return code for a NiFi not responding to ping

devs, I am reviewing PR#1093, which happens to be a great contribution towards a LSB compliant NiFi (something the overall community seems to be eager to have). The PR basically changes RunNiFi.java so that it returns a numeric exit code compatible with the LSB specifications. I am happy with

Re: Problem preparing to execute 0.7.1 release

Also, it looks like the difference between the KEYS file on dev and release prior to you adding your key to dev is that it looks like Joe Percivall's key was sort of added twice to the release repo. dev KEYS before Joe Skora addition: https://dist.apache.org/repos/dist/dev/nifi/KEYS?p=14135

Re: [DISCUSS] NiFi 1.1.0 release

Joe, Appreciate the offer it isn't my PR. I was just using it as an example. All mine are currently closed, which I greatly appreciate. Cheers, Edgardo On Friday, October 14, 2016, Joe Witt wrote: > Edgardo, > > You mentioned a PR from August. I'd be happy to help you

Re: Problem preparing to execute 0.7.1 release

I'm thinking the same thing Tony. Joe you should be able to do the full process and we just might need to help with the final push of the official bits to the release directory. In parallel please submit a request to INFRA on permissions for that folder. Perhaps there is something else I need

Re: Problem preparing to execute 0.7.1 release

I think if you can't commit or move to dist/release, the last bit of the release, (moving them over) won't work. I didn't have the issue you mentioned with the KEYS file, but I think you mentioned to me out of band the two files were different before you got started (

Re: [DISCUSS] NiFi 1.1.0 release

Edgardo, You mentioned a PR from August. I'd be happy to help you work that through review. Thanks Joe On Fri, Oct 14, 2016 at 10:45 AM, Edgardo Vega wrote: > I have agreed that at this point a release is important. My goal was try to > squeeze in a much goodness as

Re: InvokeHTTP - no relationship invoked for 502 response

Matt - Your right about just adding a "RouteOnAttribute" processor. I got so caught up in trying to understand why a retry wasn't getting fired I lost track of my original goal. I think I have a understanding of why the "retry" was not getting fired now and that makes perfect sense. I will just

Re: InvokeHTTP - no relationship invoked for 502 response

This might be intended behavior, it appears that only request (incoming) flow files get routed to relationships like "retry", but you have no incoming request flow file so there is technically nothing to retry (the processor will "retry" the next time it runs). In your case it sounds like you'd

Re: InvokeHTTP - no relationship invoked for 502 response

Matt - No, I am not seeing this expected behavior. Nothing is being routed to "retry" as expected. IF I set "Always Output Response" = true the "Response" relationship is triggered and even in there you can see the "invoke.http.statuscode=502" I have attached a screenshot to show you what I mean.

Re: InvokeHTTP - no relationship invoked for 502 response

Jeremy, The code implies that 502 responses (actually all 5xx responses) are routed to "retry" [1]. Are you not seeing that? Regards, Matt [1]

Re: Issue on creating Custom Processor - Salesforce

Shankhamajumdar - I'd be glad to help you out but how about you email me personally outside of this thread since this project isn't formally part of the Apache community. Look forward to hearing from you On Fri, Oct 14, 2016 at 8:29 AM, shankhamajumdar < shankha.majum...@lexmark.com> wrote: > Hi

Problem preparing to execute 0.7.1 release

I hit a problem working on the 0.7.1 release, I can't get my keys committed to the dist/release repository. I committed them to the dist/dev repo ( https://dist.apache.org/repos/dist/dev/nifi/KEYS) but I cannot move the file to the dist/release repo or commit directly to it, both return "403

InvokeHTTP - no relationship invoked for 502 response

I'm monitoring some micro services that sit behind an Nginx reverse proxy. The idea is simple I want to fire off an alert if I get a "502 - Bad Gateway" response from Nginx which would mean that something has caused the micro service to crash and then have NiFi attempt to restart the micro

Re: [DISCUSS] NiFi 1.1.0 release

I have agreed that at this point a release is important. My goal was try to squeeze in a much goodness as possible into the release, but the important bug fixes should come first. Getting 1.x into a state where the release notes don't say that it is geared toward developers and testers is really

Re: Issue on creating Custom Processor - Salesforce

Hi Jeremy, There is one more issue. Actually I did the build inside D:\nifi-addons-master\Services\nifi-salesforce-service\nifi-salesforce-api-nar directory successfully. But ideally I should build inside D:\nifi-addons-master\Services directory which is failing. [ERROR] [ERROR] Some problems

Re: [DISCUSS] NiFi 1.1.0 release

Edgardo, Thank you for your feedback. We hear your comments and as a committer I can share we are constantly looking to improve the PR process, having already taken many of the steps you suggest. However, it is important to notice that the number of PRs should not be seen as a metric of

Re: [DISCUSS] NiFi 1.1.0 release

Joe - You are correct I was mentioning the PRs that are currently open. Regardless of how it happens reducing the count of open PRs I believe to be extremely important. Maybe I was hoping that the release could be a forcing function to make that happen. I believe that developers are more willing

Re: Issue on creating Custom Processor - Salesforce

Thanks Jeremy, now the build is successful. Regards, Shankha -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Issue-on-creating-Custom-Processor-Salesforce-tp13603p13605.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: Issue on creating Custom Processor - Salesforce

Shankhamajumdar - You are seeing this because the Salesforce controller services haven't been built yet. If you navigate to the {nifi_addons}/services directory and run a mvn clean install and then reattempt to build the processors the error should go away. - Jeremy Dyer > On Oct 14, 2016,

Issue on creating Custom Processor - Salesforce

Hi, I am trying to create the Custom Salesforce Processor for Nifi but getting the below error while doing the maven build. [ERROR] Failed to execute goal on project nifi-salesforce-processors: Could not resolve dependencies for project com.jeremydyer.nifi:nifi-salesforce-processors: jar:1.0.0: