0

我已经创建了具有 3 个处理器的 Nifi 工作流程。附件是详细信息。问题是当我在 Nifi 中运行工作流时它运行良好，但是当我在 Kylo 中导入相同的模板并通过提要运行它时，它给出了错误。Kylo 模板似乎有问题。你能帮我解决这个问题吗？同样在 Nifi 日志中，我看不到任何错误。

谢谢，

凯洛工作失败 凯洛工作失败

尼菲工作流程 尼菲工作流程

凯洛模板-1 凯洛模板-1

凯洛模板-2

    Nifi log:

    2017-08-30 10:11:49,764 INFO [pool-8-thread-1] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@65b65bdb checkpointed with 1 Records and 0 Swap Files in 34 milliseconds (Stop-the-world time = 16 milliseconds, Clear Edit Logs time = 15 millis), max Transaction ID 37082
    2017-08-30 10:11:49,764 INFO [pool-8-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 1 records in 34 milliseconds
    2017-08-30 10:13:47,109 INFO [Write-Ahead Local State Provider Maintenance] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@2efe3a02 checkpointed with 2326 Records and 0 Swap Files in 18 milliseconds (Stop-the-world time = 1 milliseconds, Clear Edit Logs time = 1 millis), max Transaction ID 6977
    2017-08-30 10:13:49,764 INFO [pool-8-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Initiating checkpoint of FlowFile Repository
    2017-08-30 10:13:49,799 INFO [pool-8-thread-1] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@65b65bdb checkpointed with 1 Records and 0 Swap Files in 34 milliseconds (Stop-the-world time = 16 milliseconds, Clear Edit Logs time = 15 millis), max Transaction ID 37082
    2017-08-30 10:13:49,799 INFO [pool-8-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 1 records in 34 milliseconds
    2017-08-30 10:14:05,620 INFO [StandardProcessScheduler Thread-3] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ExecuteSQL[id=ef6f1e38-682f-4300-d33f-ceb1839cdf61] to run with 1 threads
    2017-08-30 10:14:06,147 INFO [Flow Service Tasks Thread-2] o.a.nifi.controller.StandardFlowService Saved flow controller org.apache.nifi.controller.FlowController@2678d4a7 // Another save pending = false
    2017-08-30 10:14:08,057 INFO [FeedStatisticsManager-SendStats-2] c.t.n.p.j.ProvenanceEventActiveMqWriter SENDING Batch Events to JMS ProvenanceEventRecordDTOHolder{events=3} 
    2017-08-30 10:14:14,951 INFO [Provenance Maintenance Thread-1] o.a.n.p.PersistentProvenanceRepository Created new Provenance Event Writers for events starting with ID 46037
    2017-08-30 10:14:14,965 INFO [Provenance Repository Rollover Thread-2] o.a.n.p.PersistentProvenanceRepository Successfully merged 16 journal files (4 records) into single Provenance Log File /opt/data/provenance_repository/46033.prov in 18 milliseconds
    2017-08-30 10:14:14,965 INFO [Provenance Repository Rollover Thread-2] o.a.n.p.PersistentProvenanceRepository Successfully Rolled over Provenance Event file containing 3 records
    2017-08-30 10:14:38,057 INFO [FeedStatisticsManager-SendStats-0] c.t.n.p.j.ProvenanceEventActiveMqWriter SENDING Batch Events to JMS ProvenanceEventRecordDTOHolder{events=3} 
    2017-08-30 10:14:44,959 INFO [Provenance Maintenance Thread-3] o.a.n.p.PersistentProvenanceRepository Created new Provenance Event Writers for events starting with ID 46041
    2017-08-30 10:14:44,999 INFO [Provenance Repository Rollover Thread-1] o.a.n.p.PersistentProvenanceRepository Successfully merged 16 journal files (4 records) into single Provenance Log File /opt/data/provenance_repository/46037.prov in 39 milliseconds
    2017-08-30 10:14:44,999 INFO [Provenance Repository Rollover Thread-1] o.a.n.p.PersistentProvenanceRepository Successfully Rolled over Provenance Event file containing 3 records
4

1 回答 1

5

Kylo 通过查看连接名称来确定流文件是否失败。由于您对失败和成功使用相同的连接，因此 Kylo 无法确定它是失败还是成功。

有几种方法可以改变这种情况：

  1. 为故障添加 PutFile 或 LogAttribute 处理器并删除现有的故障连接。如果出现故障，这将阻止流文件继续进行。

  2. 自动终止故障连接并删除现有的故障连接。这将停止流文件的进程，但由于没有失败连接，Kylo 会将所有内容显示为成功。

  3. 将您的连接重命名为“成功”。这将允许流文件继续，Kylo 将显示一切成功。

于 2017-08-30T17:28:51.487 回答