2017-08-30 82 views
0

我創建了具有3個處理器的Nifi工作流程。附加的是細節。 問題是,當我在Nifi中運行工作流程時,它運行良好,但是當我在Kylo中導入相同的模板並通過feed運行時,它發出錯誤。似乎Kylo模板出現問題。你能幫我解決這個問題嗎?同樣在Nifi日誌中,我無法看到任何錯誤。Kylo模板失敗

感謝,

Kylo作業失敗 Kylo Job Failure

Nifi工作流程 Nifi Workflow

Kylo模板-1 Kylo Template-1

Kylo Template -2

Nifi log: 

    2017-08-30 10:11:49,764 INFO [pool-8-thread-1] org.wali.MinimalLockingWriteAheadLog [email protected] 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 [email protected] 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 [email protected] 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 [email protected] // 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 
+0

日誌中的時間戳不對應於Kylo UI中的失敗時間。你能看看你是否可以匹配這兩個? Nifi日誌中必須有一些東西 –

+0

此類問題最好在Kylo Google小組上提出,因爲它不是嚴格的編程類型問題。您可以在https://groups.google.com/forum/#!forum/kylo-community –

+0

谷歌羣組上找到Kylo社區。另請參閱以下有關谷歌羣組的對話:https://groups.google.com/forum/? utm_medium =電子郵件&utm_source =頁腳#!話題/ kylo社區/ WyCN_YWPQo8 –

回答

3

Kylo通過查看連接名稱來確定流文件是否失敗。由於您使用相同的連接失敗和成功,Kylo無法確定它是失敗還是成功。

有改變這幾個方面:

  1. 添加PUTFILE或LogAttribute處理器故障,並刪除現有的失敗的連接。如果發生故障,這將停止流程文件的進展。

  2. 自動終止故障連接並刪除您現有的故障連接。這將阻止流程文件進展,但Kylo將顯示所有內容,因爲沒有失敗連接。

  3. 將您的連接重命名爲「成功」。這將允許流文件繼續,Kylo將顯示一切成功。