我有多个使用Cron驱动的调度策略运行的GetSplunk处理器. Cron表达式看起来像’0 30 13 * *？’.它们都在第一次运行时成功执行查询.但是,第二天它因Splunk的401错误而出错.来自nifi-app.log的错误如下. NiFi中的Cron调度程序是QuartzScheduler.
WARN [Timer-Driven Process Thread-7] o.a.n.c.t.ContinuallyRunProcessorTask Administratively
Yielding GetSplunk[id=01581009-026c-114b-5e2e-401ebea6427d] due to uncaught Exception:
com.splunk.HttpException: HTTP 401 -- call not properly authenticated
2016-12-21 13:30:00,300 WARN [Timer-Driven Process Thread-2] o.a.n.c.t.ContinuallyRunProcessorTask
com.splunk.HttpException: HTTP 401 -- call not properly authenticated
at com.splunk.HttpException.create(HttpException.java:84) ~[na:na]
at com.splunk.HttpService.send(HttpService.java:452) ~[na:na]
at com.splunk.Service.send(Service.java:1293) ~[na:na]
at com.splunk.HttpService.get(HttpService.java:165) ~[na:na]
at com.splunk.Service.export(Service.java:222) ~[na:na]
at com.splunk.Service.export(Service.java:237) ~[na:na]
at org.apache.nifi.processors.splunk.GetSplunk.onTrigger(GetSplunk.java:461) ~[na:na]
at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) ~[nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064) ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136) [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47) [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at org.apache.nifi.controller.scheduling.QuartzSchedulingAgent$2.run(QuartzSchedulingAgent.java:165) [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_101]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]`
GetSplunk处理器使用Java SDK for Splunk.我最早的时间是’-24h’,最近的时间是’现在’.我正在使用端口8089进行splunkd.经过一些研究,似乎这可能是一个问题,因为多线程.有没有人碰到过这个？
帮助赞赏.
解决方法:
在查看代码几分钟后,我认为这是NiFi处理器中的一个问题.
处理器第一次执行时,它懒洋洋地初始化Splunk服务对象：
作为初始化的一部分,Splunk服务调用这样的登录方法：
public Service login(String username, String password) {
this.username = username;
this.password = password;
Args args = new Args();
args.put("username", username);
args.put("password", password);
args.put("cookie", "1");
ResponseMessage response = post("/services/auth/login", args);
String sessionKey = Xml.parse(response.getContent())
.getElementsByTagName("sessionKey")
.item(0)
.getTextContent();
this.token = "Splunk " + sessionKey;
this.version = this.getInfo().getVersion();
if (versionCompare("4.3") >= 0)
this.passwordEndPoint = "storage/passwords";
return this;
}
由于这仅在处理器第一次执行时发生,因此只有在停止并启动处理器时才会再次发生.在您的情况下,您的处理器运行时间足够长,以至于会话可能已过期且处理器正在继续尝试执行.
我为这个问题创建了这个JIRA：
https://issues.apache.org/jira/browse/NIFI-3349