[jira] [Assigned] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-498: -- Assignee: Corinne Jukes (was: Aldrin Piri) > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Corinne Jukes >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161297#comment-17161297 ] Aldrin Piri commented on MINIFI-498: [~Jukes] I was not able to get it easily reproduced at the time. I've added you to the contributors and will make you the assignee on this ticket. Thanks for digging in! > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-528) Add Documentation for Minifi Arm64 Docker Image
[ https://issues.apache.org/jira/browse/MINIFI-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-528. Fix Version/s: 0.6.0 Resolution: Fixed > Add Documentation for Minifi Arm64 Docker Image > --- > > Key: MINIFI-528 > URL: https://issues.apache.org/jira/browse/MINIFI-528 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: kaustav mukherjee >Priority: Major > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-528) Add Documentation for Minifi Arm64 Docker Image
[ https://issues.apache.org/jira/browse/MINIFI-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-528: -- Assignee: kaustav mukherjee > Add Documentation for Minifi Arm64 Docker Image > --- > > Key: MINIFI-528 > URL: https://issues.apache.org/jira/browse/MINIFI-528 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: kaustav mukherjee >Assignee: kaustav mukherjee >Priority: Major > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-490) Generically support reporting tasks
[ https://issues.apache.org/jira/browse/MINIFI-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-490: -- Assignee: Nghia Le > Generically support reporting tasks > --- > > Key: MINIFI-490 > URL: https://issues.apache.org/jira/browse/MINIFI-490 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Nghia Le >Priority: Major > Fix For: 0.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MINIFI-490) Generically support reporting tasks
[ https://issues.apache.org/jira/browse/MINIFI-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134531#comment-17134531 ] Aldrin Piri commented on MINIFI-490: Commit accidentally used MINIFI-492 and history is on that issue. > Generically support reporting tasks > --- > > Key: MINIFI-490 > URL: https://issues.apache.org/jira/browse/MINIFI-490 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Nghia Le >Priority: Major > Fix For: 0.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-490) Generically support reporting tasks
[ https://issues.apache.org/jira/browse/MINIFI-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-490. Fix Version/s: 0.6.0 Resolution: Fixed > Generically support reporting tasks > --- > > Key: MINIFI-490 > URL: https://issues.apache.org/jira/browse/MINIFI-490 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-524) Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi
[ https://issues.apache.org/jira/browse/MINIFI-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-524: -- Assignee: Aldrin Piri > Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi > - > > Key: MINIFI-524 > URL: https://issues.apache.org/jira/browse/MINIFI-524 > Project: Apache NiFi MiNiFi > Issue Type: New Feature > Components: Docker >Affects Versions: 0.6.0 > Environment: UBUNTU 19.10 ARM64_V8 for Raspberry Pi 4 >Reporter: kaustav mukherjee >Assignee: Aldrin Piri >Priority: Major > Labels: ARM, Docker > Fix For: 0.6.0 > > Attachments: dockerhub_ARM_64_V8.tar.gz > > Time Spent: 2h > Remaining Estimate: 0h > > Adding ARM_V8 Docker Image for minifi java so that it can execute on Rapberry > Pi 4 abd any other edge Devices That needs to the Minifi Flow -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-524) Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi
[ https://issues.apache.org/jira/browse/MINIFI-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-524: -- Assignee: kaustav mukherjee (was: Aldrin Piri) > Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi > - > > Key: MINIFI-524 > URL: https://issues.apache.org/jira/browse/MINIFI-524 > Project: Apache NiFi MiNiFi > Issue Type: New Feature > Components: Docker >Affects Versions: 0.6.0 > Environment: UBUNTU 19.10 ARM64_V8 for Raspberry Pi 4 >Reporter: kaustav mukherjee >Assignee: kaustav mukherjee >Priority: Major > Labels: ARM, Docker > Fix For: 0.6.0 > > Attachments: dockerhub_ARM_64_V8.tar.gz > > Time Spent: 2h > Remaining Estimate: 0h > > Adding ARM_V8 Docker Image for minifi java so that it can execute on Rapberry > Pi 4 abd any other edge Devices That needs to the Minifi Flow -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-524) Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi
[ https://issues.apache.org/jira/browse/MINIFI-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-524. Resolution: Fixed > Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi > - > > Key: MINIFI-524 > URL: https://issues.apache.org/jira/browse/MINIFI-524 > Project: Apache NiFi MiNiFi > Issue Type: New Feature > Components: Docker >Affects Versions: 0.6.0 > Environment: UBUNTU 19.10 ARM64_V8 for Raspberry Pi 4 >Reporter: kaustav mukherjee >Priority: Major > Labels: ARM, Docker > Fix For: 0.6.0 > > Attachments: dockerhub_ARM_64_V8.tar.gz > > Time Spent: 2h > Remaining Estimate: 0h > > Adding ARM_V8 Docker Image for minifi java so that it can execute on Rapberry > Pi 4 abd any other edge Devices That needs to the Minifi Flow -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-526) Add anchors to MiNiFi admin guide
[ https://issues.apache.org/jira/browse/MINIFI-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-526. Resolution: Fixed > Add anchors to MiNiFi admin guide > - > > Key: MINIFI-526 > URL: https://issues.apache.org/jira/browse/MINIFI-526 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Documentation >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Add HTML anchors to admin guide so different sections are easy to reference > and link to as needed. > [https://nifi.apache.org/minifi/system-admin-guide.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-526) Add anchors to MiNiFi admin guide
[ https://issues.apache.org/jira/browse/MINIFI-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-526: --- Fix Version/s: 0.6.0 > Add anchors to MiNiFi admin guide > - > > Key: MINIFI-526 > URL: https://issues.apache.org/jira/browse/MINIFI-526 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Documentation >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Add HTML anchors to admin guide so different sections are easy to reference > and link to as needed. > [https://nifi.apache.org/minifi/system-admin-guide.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MINIFI-527) minifi agent crashing frequently with java.lang.IllegalAccessError: tried to access method org.apache.nifi.provenance.StandardProvenanceEventRecord.setEventId(J)V from
[
https://issues.apache.org/jira/browse/MINIFI-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101981#comment-17101981
]
Aldrin Piri commented on MINIFI-527:
[~Sasidhar.Jasti] could you provide some more information regarding environment
and configuration you were running?
> minifi agent crashing frequently with java.lang.IllegalAccessError: tried to
> access method
> org.apache.nifi.provenance.StandardProvenanceEventRecord.setEventId(J)V from
> class org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepositoryexception
> --
>
> Key: MINIFI-527
> URL: https://issues.apache.org/jira/browse/MINIFI-527
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Processing Configuration
>Affects Versions: 0.5.0
>Reporter: Sasidhar Jasti
>Priority: Major
>
> Minfi agents are crashing with below exceptions frequently.
> Kindly assist here.
> 2020-05-05 23:35:03,151 INFO [main] o.a.n.c.r.WriteAheadFlowFileRepository
> Initialized FlowFile Repository using 256 partitions
> 2020-05-05 23:35:03,208 WARN [main] o.a.n.p.PersistentProvenanceRepository
> Merged Journal File {} already exists; however, all partial journal files
> also exist so assuming that the merge did not finish. Repeating procedure in
> order to ensure consistency.
> 2020-05-05 23:35:05,820 INFO [main] o.a.n.p.lucene.SimpleIndexManager Index
> Writer for provenance_repository/index-1588703552000 has been returned to
> Index Manager and is no longer in use. Closing Index Writer
> 2020-05-05 23:35:05,824 ERROR [main] org.apache.nifi.minifi.MiNiFi Failure to
> launch MiNiFi due to java.lang.IllegalAccessError: tried to access method
> org.apache.nifi.provenance.StandardProvenanceEventRecord.setEventId(J)V from
> class org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepository
> java.lang.IllegalAccessError: tried to access method
> org.apache.nifi.provenance.StandardProvenanceEventRecord.setEventId(J)V from
> class org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepository
> at
> org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepository.truncateAttributes(MiNiFiPersistentProvenanceRepository.java:1880)
> at
> org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepository.mergeJournals(MiNiFiPersistentProvenanceRepository.java:1731)
> at
> org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepository.recoverJournalFiles(MiNiFiPersistentProvenanceRepository.java:1427)
> at
> org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepository.recover(MiNiFiPersistentProvenanceRepository.java:587)
> at
> org.apache.nifi.provenance.MiNiFiPersistentProvenanceRepository.initialize(MiNiFiPersistentProvenanceRepository.java:254)
> at org.apache.nifi.controller.FlowController.(FlowController.java:509)
> at
> org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:422)
> at org.apache.nifi.minifi.MiNiFiServer.start(MiNiFiServer.java:102)
> at org.apache.nifi.minifi.MiNiFi.(MiNiFi.java:148)
> at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:247)
> 2020-05-05 23:35:05,830 INFO [Thread-1] org.apache.nifi.minifi.MiNiFi
> Initiating shutdown of MiNiFi server...
> 2020-05-05 23:35:05,830 WARN [Thread-1] org.apache.nifi.minifi.MiNiFiServer
> Problem occurred ensuring flow controller or repository was properly
> terminated due to java.lang.NullPointerException
> 2020-05-05 23:35:05,833 ERROR [Thread-1] org.apache.nifi.BootstrapListener
> Failed to communicate with Bootstrap. Bootstrap may be unable to issue or
> receive commands from MiNiFi
> 2020-05-05 23:35:05,833 INFO [Thread-1] org.apache.nifi.minifi.MiNiFi MiNiFi
> server shutdown completed (nicely or otherwise).
>
> Thanks,
> Sasi
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062592#comment-17062592
]
Aldrin Piri commented on MINIFI-521:
Confirmed the expected config.yml is not quite right. Used the buggy xml with
the changes applied and was able to successfully transmit. Will update the
files and get the associated tests enabled.
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml, config.yml, minifi-flow.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062566#comment-17062566
]
Aldrin Piri commented on MINIFI-521:
[~tjfleming] [~tugenhao]
I have a WIP branch (as I need to make some tests) available with PR
[https://github.com/apache/nifi-minifi/pull/185]
The file supplied for the expected yml is not correct, however, using the code
change I was able to confirm successful transform and transmission for a local
instance. This transform was from minifi-flow.xml -> config.yml
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml, config.yml, minifi-flow.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated MINIFI-521:
---
Attachment: config.yml
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml, config.yml, minifi-flow.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated MINIFI-521:
---
Attachment: minifi-flow.xml
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml, minifi-flow.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reassigned MINIFI-521:
--
Assignee: Aldrin Piri
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml
>
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (MINIFI-522) Fixed Access denied to: http://jcenter.bintray.com which caused Failed to execute goal on project minifi-standard-nar
[
https://issues.apache.org/jira/browse/MINIFI-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri resolved MINIFI-522.
Resolution: Fixed
> Fixed Access denied to: http://jcenter.bintray.com which caused Failed to
> execute goal on project minifi-standard-nar
> -
>
> Key: MINIFI-522
> URL: https://issues.apache.org/jira/browse/MINIFI-522
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: sapinkumar amin
>Assignee: sapinkumar amin
>Priority: Blocker
> Fix For: 0.6.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> mvn clean install {code}
> throws below error
> {code:java}
> [INFO] minifi-update-attribute-nar SUCCESS [ 0.326
> s]
> [INFO] minifi-standard-nar FAILURE [ 1.198
> s]
> [INFO] minifi-ssl-context-service-nar . SKIPPED
> [INFO] minifi-docs SKIPPED
> [INFO] minifi-assembly SKIPPED
> [INFO] minifi-toolkit . SKIPPED
> [INFO] minifi-toolkit-configuration ... SKIPPED
> [INFO] minifi-toolkit-assembly SKIPPED
> [INFO] minifi-docker .. SKIPPED
> [INFO] minifi-c2 .. SKIPPED
> [INFO] minifi-c2-api .. SKIPPED
> [INFO] minifi-c2-cache SKIPPED
> [INFO] minifi-c2-cache-filesystem . SKIPPED
> [INFO] minifi-c2-cache-s3 . SKIPPED
> [INFO] minifi-c2-provider . SKIPPED
> [INFO] minifi-c2-provider-util SKIPPED
> [INFO] minifi-c2-provider-cache ... SKIPPED
> [INFO] minifi-c2-provider-delegating .. SKIPPED
> [INFO] minifi-c2-provider-nifi-rest ... SKIPPED
> [INFO] minifi-c2-service .. SKIPPED
> [INFO] minifi-c2-jetty SKIPPED
> [INFO] minifi-c2-assembly . SKIPPED
> [INFO] minifi-c2-docker ... SKIPPED
> [INFO] minifi-c2-integration-tests SKIPPED
> [INFO] minifi-integration-tests ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29.209 s
> [INFO] Finished at: 2020-01-14T14:02:00-08:00
> [INFO]
>
> [ERROR] Failed to execute goal on project minifi-standard-nar: Could not
> resolve dependencies for project
> org.apache.nifi.minifi:minifi-standard-nar:nar:0.6.0-SNAPSHOT: Failed to
> collect dependencies at org.apache.nifi:nifi-standard-processors:jar:1.8.0 ->
> org.apache.nifi:nifi-syslog-utils:jar:1.8.0 ->
> com.github.palindromicity:simple-syslog-5424:jar:0.0.8: Failed to read
> artifact descriptor for
> com.github.palindromicity:simple-syslog-5424:jar:0.0.8: Could not transfer
> artifact com.github.palindromicity:simple-syslog-5424:pom:0.0.8 from/to
> jcenter (http://jcenter.bintray.com): Access denied to:
> http://jcenter.bintray.com/com/github/palindromicity/simple-syslog-5424/0.0.8/simple-syslog-5424-0.0.8.pom
> -> [Help 1]
> {code}
>
> From Jan13th : 2020 , access to jcenter.bintray.com is only allowed over
> https protocol (previously it use to support http and https).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MINIFI-522) Fixed Access denied to: http://jcenter.bintray.com which caused Failed to execute goal on project minifi-standard-nar
[
https://issues.apache.org/jira/browse/MINIFI-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reassigned MINIFI-522:
--
Assignee: sapinkumar amin
> Fixed Access denied to: http://jcenter.bintray.com which caused Failed to
> execute goal on project minifi-standard-nar
> -
>
> Key: MINIFI-522
> URL: https://issues.apache.org/jira/browse/MINIFI-522
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: sapinkumar amin
>Assignee: sapinkumar amin
>Priority: Blocker
> Fix For: 0.6.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> mvn clean install {code}
> throws below error
> {code:java}
> [INFO] minifi-update-attribute-nar SUCCESS [ 0.326
> s]
> [INFO] minifi-standard-nar FAILURE [ 1.198
> s]
> [INFO] minifi-ssl-context-service-nar . SKIPPED
> [INFO] minifi-docs SKIPPED
> [INFO] minifi-assembly SKIPPED
> [INFO] minifi-toolkit . SKIPPED
> [INFO] minifi-toolkit-configuration ... SKIPPED
> [INFO] minifi-toolkit-assembly SKIPPED
> [INFO] minifi-docker .. SKIPPED
> [INFO] minifi-c2 .. SKIPPED
> [INFO] minifi-c2-api .. SKIPPED
> [INFO] minifi-c2-cache SKIPPED
> [INFO] minifi-c2-cache-filesystem . SKIPPED
> [INFO] minifi-c2-cache-s3 . SKIPPED
> [INFO] minifi-c2-provider . SKIPPED
> [INFO] minifi-c2-provider-util SKIPPED
> [INFO] minifi-c2-provider-cache ... SKIPPED
> [INFO] minifi-c2-provider-delegating .. SKIPPED
> [INFO] minifi-c2-provider-nifi-rest ... SKIPPED
> [INFO] minifi-c2-service .. SKIPPED
> [INFO] minifi-c2-jetty SKIPPED
> [INFO] minifi-c2-assembly . SKIPPED
> [INFO] minifi-c2-docker ... SKIPPED
> [INFO] minifi-c2-integration-tests SKIPPED
> [INFO] minifi-integration-tests ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29.209 s
> [INFO] Finished at: 2020-01-14T14:02:00-08:00
> [INFO]
>
> [ERROR] Failed to execute goal on project minifi-standard-nar: Could not
> resolve dependencies for project
> org.apache.nifi.minifi:minifi-standard-nar:nar:0.6.0-SNAPSHOT: Failed to
> collect dependencies at org.apache.nifi:nifi-standard-processors:jar:1.8.0 ->
> org.apache.nifi:nifi-syslog-utils:jar:1.8.0 ->
> com.github.palindromicity:simple-syslog-5424:jar:0.0.8: Failed to read
> artifact descriptor for
> com.github.palindromicity:simple-syslog-5424:jar:0.0.8: Could not transfer
> artifact com.github.palindromicity:simple-syslog-5424:pom:0.0.8 from/to
> jcenter (http://jcenter.bintray.com): Access denied to:
> http://jcenter.bintray.com/com/github/palindromicity/simple-syslog-5424/0.0.8/simple-syslog-5424-0.0.8.pom
> -> [Help 1]
> {code}
>
> From Jan13th : 2020 , access to jcenter.bintray.com is only allowed over
> https protocol (previously it use to support http and https).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (MINIFI-516) Override processor SSLs with parent SSL
[ https://issues.apache.org/jira/browse/MINIFI-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-516. Fix Version/s: 0.6.0 Resolution: Fixed > Override processor SSLs with parent SSL > --- > > Key: MINIFI-516 > URL: https://issues.apache.org/jira/browse/MINIFI-516 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: GCHQ NiFi >Assignee: r65535 >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > When using a ingestor to deploy flows to MiNiFi, processors using SSL > contexts don't start up as the sensitive properties are not passed along in > the NiFi templates. > A user should be able to set a boolean in the bootstrap.conf to tell MiNiFi > to ignore any custom SSL contexts in the config.yml, and repoint to the > parent SSL called "SSL-Context-Service" instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reassigned MINIFI-521:
--
Assignee: (was: Aldrin Piri)
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml
>
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998455#comment-16998455
]
Aldrin Piri commented on MINIFI-521:
Definitely was a change, but thankfully the associated template encoding
version was also bumped. Will need to reason about the changes but basing
handling on that determination should be able to get us there.
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml
>
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reassigned MINIFI-521:
--
Assignee: Aldrin Piri
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml
>
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (MINIFI-519) Add recommendations for antivirus exclusions to Admin guide
[ https://issues.apache.org/jira/browse/MINIFI-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-519. Resolution: Fixed > Add recommendations for antivirus exclusions to Admin guide > --- > > Key: MINIFI-519 > URL: https://issues.apache.org/jira/browse/MINIFI-519 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Add similar section regarding antivirus exclusions to MiNiFi Admin Guide that > was added to NiFi Admin Guide via NIFI-6553 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFI-520) Migrate Docker image names to mirror those of the public repos
Aldrin Piri created MINIFI-520: -- Summary: Migrate Docker image names to mirror those of the public repos Key: MINIFI-520 URL: https://issues.apache.org/jira/browse/MINIFI-520 Project: Apache NiFi MiNiFi Issue Type: Improvement Reporter: Aldrin Piri Assignee: Aldrin Piri For consistency, it would be helpful to have the docker images reflect the image tags used in Docker Hub. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-519) Add recommendations for antivirus exclusions to Admin guide
[ https://issues.apache.org/jira/browse/MINIFI-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-519: --- Fix Version/s: 0.6.0 > Add recommendations for antivirus exclusions to Admin guide > --- > > Key: MINIFI-519 > URL: https://issues.apache.org/jira/browse/MINIFI-519 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Add similar section regarding antivirus exclusions to MiNiFi Admin Guide that > was added to NiFi Admin Guide via NIFI-6553 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-518) Version issue with httpcomponents
[ https://issues.apache.org/jira/browse/MINIFI-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-518. Resolution: Fixed > Version issue with httpcomponents > - > > Key: MINIFI-518 > URL: https://issues.apache.org/jira/browse/MINIFI-518 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Build >Affects Versions: 0.6.0 >Reporter: James >Assignee: James >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The version of httpcomponents in the latest 0.6.0 pom causes and issue with > using a postHTTP with a security context defined (although I think its > generic to anything trying to use the SSLContextBuilder class). > The pom currently references; > > org.apache.httpcomponents > httpcore > 4.4.4 > > > But need to reference a later version, 4.4.12 works and is the latest. > I'll create a pull request so you can test the updated version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-518) Version issue with httpcomponents
[ https://issues.apache.org/jira/browse/MINIFI-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-518: -- Assignee: James > Version issue with httpcomponents > - > > Key: MINIFI-518 > URL: https://issues.apache.org/jira/browse/MINIFI-518 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Build >Affects Versions: 0.6.0 >Reporter: James >Assignee: James >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > The version of httpcomponents in the latest 0.6.0 pom causes and issue with > using a postHTTP with a security context defined (although I think its > generic to anything trying to use the SSLContextBuilder class). > The pom currently references; > > org.apache.httpcomponents > httpcore > 4.4.4 > > > But need to reference a later version, 4.4.12 works and is the latest. > I'll create a pull request so you can test the updated version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-518) Version issue with httpcomponents
[ https://issues.apache.org/jira/browse/MINIFI-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-518: --- Fix Version/s: 0.6.0 > Version issue with httpcomponents > - > > Key: MINIFI-518 > URL: https://issues.apache.org/jira/browse/MINIFI-518 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Build >Affects Versions: 0.6.0 >Reporter: James >Assignee: James >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The version of httpcomponents in the latest 0.6.0 pom causes and issue with > using a postHTTP with a security context defined (although I think its > generic to anything trying to use the SSLContextBuilder class). > The pom currently references; > > org.apache.httpcomponents > httpcore > 4.4.4 > > > But need to reference a later version, 4.4.12 works and is the latest. > I'll create a pull request so you can test the updated version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFI-515) Make use of new location for commons-daemon
Aldrin Piri created MINIFI-515: -- Summary: Make use of new location for commons-daemon Key: MINIFI-515 URL: https://issues.apache.org/jira/browse/MINIFI-515 Project: Apache NiFi MiNiFi Issue Type: Improvement Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.6.0 Related to MINIFI-508 and MINIFI-514. Plan to make use of a mirrored repository to have a consistent location and not make builds so fragile when releases occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-507) Audit MiNiFi dependencies for upgrade
[ https://issues.apache.org/jira/browse/MINIFI-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-507: --- Fix Version/s: 0.6.0 > Audit MiNiFi dependencies for upgrade > - > > Key: MINIFI-507 > URL: https://issues.apache.org/jira/browse/MINIFI-507 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Nathan Gough >Priority: Major > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Check the MiNiFi project for dependencies that need to be upgraded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-507) Audit MiNiFi dependencies for upgrade
[ https://issues.apache.org/jira/browse/MINIFI-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-507. Assignee: Nathan Gough Resolution: Fixed > Audit MiNiFi dependencies for upgrade > - > > Key: MINIFI-507 > URL: https://issues.apache.org/jira/browse/MINIFI-507 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Nathan Gough >Assignee: Nathan Gough >Priority: Major > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Check the MiNiFi project for dependencies that need to be upgraded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MINIFI-508) Make Windows daemon inclusion a profile
[ https://issues.apache.org/jira/browse/MINIFI-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938782#comment-16938782 ] Aldrin Piri commented on MINIFI-508: As a result of MINIFI-514 it is time to address this. > Make Windows daemon inclusion a profile > --- > > Key: MINIFI-508 > URL: https://issues.apache.org/jira/browse/MINIFI-508 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Affects Versions: 0.5.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > > As the Windows service executable relies on an outside source it could be > beneficial to have this process driven by a profile to mitigate those areas > where users do not care about having that support. The intent would be for > this to still remain in released convenience binaries as part of the RM > process but make it disabled by default -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFI-514) Update commons-daemon to 1.2.1
Aldrin Piri created MINIFI-514: -- Summary: Update commons-daemon to 1.2.1 Key: MINIFI-514 URL: https://issues.apache.org/jira/browse/MINIFI-514 Project: Apache NiFi MiNiFi Issue Type: Task Affects Versions: 0.5.0 Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.6.0 Commons-daemon had a bugfix release and we will need to perform another update as the prior version has rolled off many mirrors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-508) Make Windows daemon inclusion a profile
[ https://issues.apache.org/jira/browse/MINIFI-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-508: --- Fix Version/s: 0.6.0 > Make Windows daemon inclusion a profile > --- > > Key: MINIFI-508 > URL: https://issues.apache.org/jira/browse/MINIFI-508 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Affects Versions: 0.5.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > > As the Windows service executable relies on an outside source it could be > beneficial to have this process driven by a profile to mitigate those areas > where users do not care about having that support. The intent would be for > this to still remain in released convenience binaries as part of the RM > process but make it disabled by default -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-508) Make Windows daemon inclusion a profile
[ https://issues.apache.org/jira/browse/MINIFI-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-508: -- Assignee: Aldrin Piri > Make Windows daemon inclusion a profile > --- > > Key: MINIFI-508 > URL: https://issues.apache.org/jira/browse/MINIFI-508 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Affects Versions: 0.5.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > > As the Windows service executable relies on an outside source it could be > beneficial to have this process driven by a profile to mitigate those areas > where users do not care about having that support. The intent would be for > this to still remain in released convenience binaries as part of the RM > process but make it disabled by default -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MINIFI-513) CLONE - Updated bootstrap port handling causes restarts to fail
[
https://issues.apache.org/jira/browse/MINIFI-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938083#comment-16938083
]
Aldrin Piri commented on MINIFI-513:
Introduced into this codebase by MINIFI-512
> CLONE - Updated bootstrap port handling causes restarts to fail
> ---
>
> Key: MINIFI-513
> URL: https://issues.apache.org/jira/browse/MINIFI-513
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Blocker
> Fix For: 0.6.0
>
>
> NIFI-6653 introduced a way to avoid the port being changed to prevent a
> possible hijacking of that port to provide other commands than those
> explicitly between bootstrap and the nifi process. This causes issues when
> the NiFi process dies and precludes restart (the default functionality
> enabled out of the box).
> To recreate, build/run NiFi off of current master and kill the NiFi process.
> This will result in the following (when an additional nifi.sh status is
> carried out).
> {quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
> Apache NiFi appears to have died. Restarting...
> 2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 2088
> 2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Successfully started Apache NiFi with PID 2088
> 2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
> org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command
> port and secret after they have already been initialized. requestedPort=37871
> 2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
> Successfully loaded the following 0 services: []
> 2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STARTED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STOPPED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_DIED
> 2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
> NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Moved] (MINIFI-513) CLONE - Updated bootstrap port handling causes restarts to fail
[
https://issues.apache.org/jira/browse/MINIFI-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri moved NIFI-6713 to MINIFI-513:
--
Fix Version/s: (was: 1.10.0)
0.6.0
Key: MINIFI-513 (was: NIFI-6713)
Project: Apache NiFi MiNiFi (was: Apache NiFi)
> CLONE - Updated bootstrap port handling causes restarts to fail
> ---
>
> Key: MINIFI-513
> URL: https://issues.apache.org/jira/browse/MINIFI-513
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Blocker
> Fix For: 0.6.0
>
>
> NIFI-6653 introduced a way to avoid the port being changed to prevent a
> possible hijacking of that port to provide other commands than those
> explicitly between bootstrap and the nifi process. This causes issues when
> the NiFi process dies and precludes restart (the default functionality
> enabled out of the box).
> To recreate, build/run NiFi off of current master and kill the NiFi process.
> This will result in the following (when an additional nifi.sh status is
> carried out).
> {quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
> Apache NiFi appears to have died. Restarting...
> 2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 2088
> 2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Successfully started Apache NiFi with PID 2088
> 2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
> org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command
> port and secret after they have already been initialized. requestedPort=37871
> 2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
> Successfully loaded the following 0 services: []
> 2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STARTED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STOPPED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_DIED
> 2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
> NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MINIFI-511) Allow Provenance Reporting to be configured outside of the config.yml
[ https://issues.apache.org/jira/browse/MINIFI-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-511: -- Assignee: GCHQ NiFi > Allow Provenance Reporting to be configured outside of the config.yml > - > > Key: MINIFI-511 > URL: https://issues.apache.org/jira/browse/MINIFI-511 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Agent Configuration/Installation >Reporter: GCHQ NiFi >Assignee: GCHQ NiFi >Priority: Major > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When using the MiNiFi config change notifiers, it's not currently possible to > set the provenance reporting properties. > MINIFI-501 allowed for the SSL context properties to be set in the bootstrap, > so it makes sense for the provenance reporting to be set in the same way. > I've created a fork with the changes completed already, so will link this > ticket to a pull request. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (MINIFI-509) SSL Context defined in bootstrap Not Working?
[
https://issues.apache.org/jira/browse/MINIFI-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated MINIFI-509:
---
Fix Version/s: 0.6.0
> SSL Context defined in bootstrap Not Working?
> -
>
> Key: MINIFI-509
> URL: https://issues.apache.org/jira/browse/MINIFI-509
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Ryan Whittington
>Assignee: Ferenc Kis
>Priority: Major
> Fix For: 0.6.0
>
>
> I'm trying to set my SSL-Context-Service properties using the bootstrap.conf,
> but it doesn't seem to propagate through to the flow.xml.gz when minifi
> starts/reloads - and isn't available to use in my flow?
> As this feature was recently added in MINIFI-501 by [~aldrin], I'm building
> minifi from the master branch on github.
> bootstrap.conf:
>
> {code:java}
> # Security Properties #
> # These properties take precedence over any equivalent properties specified
> in config.yml #
> nifi.minifi.security.keystore=/my/test/keystore.jks
> nifi.minifi.security.keystoreType=JKS
> nifi.minifi.security.keystorePasswd=mykeystorepassword
> nifi.minifi.security.keyPasswd=mykeypassword
> nifi.minifi.security.truststore=/my/test/truststore.jks
> nifi.minifi.security.truststoreType=JKS
> nifi.minifi.security.truststorePasswd=mytruststorepassword
> nifi.minifi.security.ssl.protocol=TLS
> {code}
>
> flow.xml.gz once running:
> {noformat}
>
>
> 1
> 1
>
>
> Root-Group
> MiNiFi Flow
>
>
>
>
>
> {noformat}
> Am I doing something wrong, or is this not fully implemented yet?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (MINIFI-509) SSL Context defined in bootstrap Not Working?
[
https://issues.apache.org/jira/browse/MINIFI-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reassigned MINIFI-509:
--
Assignee: Ferenc Kis (was: Aldrin Piri)
> SSL Context defined in bootstrap Not Working?
> -
>
> Key: MINIFI-509
> URL: https://issues.apache.org/jira/browse/MINIFI-509
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Ryan Whittington
>Assignee: Ferenc Kis
>Priority: Major
>
> I'm trying to set my SSL-Context-Service properties using the bootstrap.conf,
> but it doesn't seem to propagate through to the flow.xml.gz when minifi
> starts/reloads - and isn't available to use in my flow?
> As this feature was recently added in MINIFI-501 by [~aldrin], I'm building
> minifi from the master branch on github.
> bootstrap.conf:
>
> {code:java}
> # Security Properties #
> # These properties take precedence over any equivalent properties specified
> in config.yml #
> nifi.minifi.security.keystore=/my/test/keystore.jks
> nifi.minifi.security.keystoreType=JKS
> nifi.minifi.security.keystorePasswd=mykeystorepassword
> nifi.minifi.security.keyPasswd=mykeypassword
> nifi.minifi.security.truststore=/my/test/truststore.jks
> nifi.minifi.security.truststoreType=JKS
> nifi.minifi.security.truststorePasswd=mytruststorepassword
> nifi.minifi.security.ssl.protocol=TLS
> {code}
>
> flow.xml.gz once running:
> {noformat}
>
>
> 1
> 1
>
>
> Root-Group
> MiNiFi Flow
>
>
>
>
>
> {noformat}
> Am I doing something wrong, or is this not fully implemented yet?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (MINIFI-510) Migrate Travis away from OracleJDK8 which seems to be problematic
[ https://issues.apache.org/jira/browse/MINIFI-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906366#comment-16906366 ] Aldrin Piri commented on MINIFI-510: Example build issue: https://travis-ci.org/apache/nifi-minifi/jobs/571358468 > Migrate Travis away from OracleJDK8 which seems to be problematic > - > > Key: MINIFI-510 > URL: https://issues.apache.org/jira/browse/MINIFI-510 > Project: Apache NiFi MiNiFi > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > > It seems configuration of Travis has changed such that Oracle JDK 8 is no > longer available. We should migrate to supported versions of 8. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (MINIFI-510) Migrate Travis away from OracleJDK8 which seems to be problematic
Aldrin Piri created MINIFI-510: -- Summary: Migrate Travis away from OracleJDK8 which seems to be problematic Key: MINIFI-510 URL: https://issues.apache.org/jira/browse/MINIFI-510 Project: Apache NiFi MiNiFi Issue Type: Task Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.6.0 It seems configuration of Travis has changed such that Oracle JDK 8 is no longer available. We should migrate to supported versions of 8. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MINIFI-509) SSL Context defined in bootstrap Not Working?
[
https://issues.apache.org/jira/browse/MINIFI-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906324#comment-16906324
]
Aldrin Piri commented on MINIFI-509:
https://github.com/apache/nifi-minifi/pull/164
> SSL Context defined in bootstrap Not Working?
> -
>
> Key: MINIFI-509
> URL: https://issues.apache.org/jira/browse/MINIFI-509
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Ryan Whittington
>Assignee: Aldrin Piri
>Priority: Major
>
> I'm trying to set my SSL-Context-Service properties using the bootstrap.conf,
> but it doesn't seem to propagate through to the flow.xml.gz when minifi
> starts/reloads - and isn't available to use in my flow?
> As this feature was recently added in MINIFI-501 by [~aldrin], I'm building
> minifi from the master branch on github.
> bootstrap.conf:
>
> {code:java}
> # Security Properties #
> # These properties take precedence over any equivalent properties specified
> in config.yml #
> nifi.minifi.security.keystore=/my/test/keystore.jks
> nifi.minifi.security.keystoreType=JKS
> nifi.minifi.security.keystorePasswd=mykeystorepassword
> nifi.minifi.security.keyPasswd=mykeypassword
> nifi.minifi.security.truststore=/my/test/truststore.jks
> nifi.minifi.security.truststoreType=JKS
> nifi.minifi.security.truststorePasswd=mytruststorepassword
> nifi.minifi.security.ssl.protocol=TLS
> {code}
>
> flow.xml.gz once running:
> {noformat}
>
>
> 1
> 1
>
>
> Root-Group
> MiNiFi Flow
>
>
>
>
>
> {noformat}
> Am I doing something wrong, or is this not fully implemented yet?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (MINIFI-509) SSL Context defined in bootstrap Not Working?
[
https://issues.apache.org/jira/browse/MINIFI-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898838#comment-16898838
]
Aldrin Piri commented on MINIFI-509:
Hi there,
Thanks for reporting this. It is certainly not you and believe something may
have been blundered with the merge.
> SSL Context defined in bootstrap Not Working?
> -
>
> Key: MINIFI-509
> URL: https://issues.apache.org/jira/browse/MINIFI-509
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Ryan Whittington
>Assignee: Aldrin Piri
>Priority: Major
>
> I'm trying to set my SSL-Context-Service properties using the bootstrap.conf,
> but it doesn't seem to propagate through to the flow.xml.gz when minifi
> starts/reloads - and isn't available to use in my flow?
> As this feature was recently added in MINIFI-501 by [~aldrin], I'm building
> minifi from the master branch on github.
> bootstrap.conf:
>
> {code:java}
> # Security Properties #
> # These properties take precedence over any equivalent properties specified
> in config.yml #
> nifi.minifi.security.keystore=/my/test/keystore.jks
> nifi.minifi.security.keystoreType=JKS
> nifi.minifi.security.keystorePasswd=mykeystorepassword
> nifi.minifi.security.keyPasswd=mykeypassword
> nifi.minifi.security.truststore=/my/test/truststore.jks
> nifi.minifi.security.truststoreType=JKS
> nifi.minifi.security.truststorePasswd=mytruststorepassword
> nifi.minifi.security.ssl.protocol=TLS
> {code}
>
> flow.xml.gz once running:
> {noformat}
>
>
> 1
> 1
>
>
> Root-Group
> MiNiFi Flow
>
>
>
>
>
> {noformat}
> Am I doing something wrong, or is this not fully implemented yet?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (MINIFI-509) SSL Context defined in bootstrap Not Working?
[
https://issues.apache.org/jira/browse/MINIFI-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reassigned MINIFI-509:
--
Assignee: Aldrin Piri
> SSL Context defined in bootstrap Not Working?
> -
>
> Key: MINIFI-509
> URL: https://issues.apache.org/jira/browse/MINIFI-509
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Ryan Whittington
>Assignee: Aldrin Piri
>Priority: Major
>
> I'm trying to set my SSL-Context-Service properties using the bootstrap.conf,
> but it doesn't seem to propagate through to the flow.xml.gz when minifi
> starts/reloads - and isn't available to use in my flow?
> As this feature was recently added in MINIFI-501 by [~aldrin], I'm building
> minifi from the master branch on github.
> bootstrap.conf:
>
> {code:java}
> # Security Properties #
> # These properties take precedence over any equivalent properties specified
> in config.yml #
> nifi.minifi.security.keystore=/my/test/keystore.jks
> nifi.minifi.security.keystoreType=JKS
> nifi.minifi.security.keystorePasswd=mykeystorepassword
> nifi.minifi.security.keyPasswd=mykeypassword
> nifi.minifi.security.truststore=/my/test/truststore.jks
> nifi.minifi.security.truststoreType=JKS
> nifi.minifi.security.truststorePasswd=mytruststorepassword
> nifi.minifi.security.ssl.protocol=TLS
> {code}
>
> flow.xml.gz once running:
> {noformat}
>
>
> 1
> 1
>
>
> Root-Group
> MiNiFi Flow
>
>
>
>
>
> {noformat}
> Am I doing something wrong, or is this not fully implemented yet?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (MINIFI-508) Make Windows daemon inclusion a profile
Aldrin Piri created MINIFI-508: -- Summary: Make Windows daemon inclusion a profile Key: MINIFI-508 URL: https://issues.apache.org/jira/browse/MINIFI-508 Project: Apache NiFi MiNiFi Issue Type: Improvement Components: Build Affects Versions: 0.5.0 Reporter: Aldrin Piri As the Windows service executable relies on an outside source it could be beneficial to have this process driven by a profile to mitigate those areas where users do not care about having that support. The intent would be for this to still remain in released convenience binaries as part of the RM process but make it disabled by default -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (MINIFI-505) Change digest algorithm to SHA-512
[ https://issues.apache.org/jira/browse/MINIFI-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-505. Resolution: Fixed Assignee: Nenad V. Nikolić Fix Version/s: 0.6.0 > Change digest algorithm to SHA-512 > -- > > Key: MINIFI-505 > URL: https://issues.apache.org/jira/browse/MINIFI-505 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Nenad V. Nikolić >Assignee: Nenad V. Nikolić >Priority: Major > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > In the light of a digest algorithm change in the [PR > #157|https://github.com/apache/nifi-minifi/pull/157/commits/c13e286fdf380f315a7951573edd7d475b74372f#diff-081c5543514deb23ccd8543465113b8dR70] > from [~aldrin] and our agreement in PR #161 to keep that change separate > from the rest, the digest algorithm should be changed separately. > PR is coming shortly after PR #161 is approved and merged to master. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (MINIFI-502) Update the Windows commons daemon download URL
[ https://issues.apache.org/jira/browse/MINIFI-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-502. Resolution: Done > Update the Windows commons daemon download URL > -- > > Key: MINIFI-502 > URL: https://issues.apache.org/jira/browse/MINIFI-502 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Reporter: Jeff Zemerick >Priority: Major > > Update the URL of the Windows commons daemon zip in minifi-assembly/pom.xml. > It is currently set to > [https://apache.claz.org/commons/daemon/binaries/windows/commons-daemon-1.1.0-bin-windows.zip] > and it is not 100% reliable and often causes the build on Windows to fail. > Change the URL to > [https://www.apache.org/dist/commons/daemon/binaries/windows/commons-daemon-1.1.0-bin-windows.zip.] > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MINIFI-502) Update the Windows commons daemon download URL
[ https://issues.apache.org/jira/browse/MINIFI-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883275#comment-16883275 ] Aldrin Piri commented on MINIFI-502: Didn't see this one when reviewing the other items but we have addressed the versioning issue. As highlighted in the one PR comment (https://github.com/apache/nifi-minifi/pull/157#discussion_r301612041) I don't think using the dist offering of things for wide consumption would be suggested by INFRA. I am going to close this for those reasons but please let me know if you have a different perspective on those matters. > Update the Windows commons daemon download URL > -- > > Key: MINIFI-502 > URL: https://issues.apache.org/jira/browse/MINIFI-502 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Reporter: Jeff Zemerick >Priority: Major > > Update the URL of the Windows commons daemon zip in minifi-assembly/pom.xml. > It is currently set to > [https://apache.claz.org/commons/daemon/binaries/windows/commons-daemon-1.1.0-bin-windows.zip] > and it is not 100% reliable and often causes the build on Windows to fail. > Change the URL to > [https://www.apache.org/dist/commons/daemon/binaries/windows/commons-daemon-1.1.0-bin-windows.zip.] > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (MINIFI-506) Change minifi-assembly antrun "tasks" tags to "target"
Aldrin Piri created MINIFI-506: -- Summary: Change minifi-assembly antrun "tasks" tags to "target" Key: MINIFI-506 URL: https://issues.apache.org/jira/browse/MINIFI-506 Project: Apache NiFi MiNiFi Issue Type: Improvement Components: Build Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.6.0 "tasks" is deprecated as per the plugin. [WARNING] Parameter tasks is deprecated, use target instead -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (MINIFI-478) OrderedPropertiesTest fails on Java 11 / OS X
[ https://issues.apache.org/jira/browse/MINIFI-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-478: --- Fix Version/s: 0.6.0 > OrderedPropertiesTest fails on Java 11 / OS X > - > > Key: MINIFI-478 > URL: https://issues.apache.org/jira/browse/MINIFI-478 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Dustin Rodrigues >Assignee: Nenad V. Nikolić >Priority: Major > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When running on OS X 10.14 ( Mojave ) with openjdk 11, the > OrderedPropertiesTest is failing. When using jdk1.8.0_192 instead, the test > succeeds. > > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.05 sec <<< > FAILURE! - in org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest > testOrderedProperties(org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest) > Time elapsed: 0.05 sec <<< FAILURE! > org.junit.ComparisonFailure: expected:<[prop1=newVal1]> but was:<[#this is > property 2]> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest.testOrderedProperties(OrderedPropertiesTest.java:49) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-478) OrderedPropertiesTest fails on Java 11 / OS X
[ https://issues.apache.org/jira/browse/MINIFI-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-478: -- Assignee: Nenad V. Nikolić > OrderedPropertiesTest fails on Java 11 / OS X > - > > Key: MINIFI-478 > URL: https://issues.apache.org/jira/browse/MINIFI-478 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Dustin Rodrigues >Assignee: Nenad V. Nikolić >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > When running on OS X 10.14 ( Mojave ) with openjdk 11, the > OrderedPropertiesTest is failing. When using jdk1.8.0_192 instead, the test > succeeds. > > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.05 sec <<< > FAILURE! - in org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest > testOrderedProperties(org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest) > Time elapsed: 0.05 sec <<< FAILURE! > org.junit.ComparisonFailure: expected:<[prop1=newVal1]> but was:<[#this is > property 2]> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest.testOrderedProperties(OrderedPropertiesTest.java:49) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-504) Upgrade commons-deamon to 1.2.0 to make build green again
[
https://issues.apache.org/jira/browse/MINIFI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881418#comment-16881418
]
Aldrin Piri commented on MINIFI-504:
Hey [~shonzilla]! No problem, we are happy to have you and I will always prefer
over-reporting as opposed to not reporting :)
I left you a note on your PR
https://github.com/apache/nifi-minifi/pull/161#issuecomment-509722142 but had
opened a similar PR last evening. Let me know your thoughts and we can get
this wrapped up. I will scope out your other PR soon!
Thank you!
> Upgrade commons-deamon to 1.2.0 to make build green again
> -
>
> Key: MINIFI-504
> URL: https://issues.apache.org/jira/browse/MINIFI-504
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.6.0
>Reporter: Nenad Nikolic
>Priority: Blocker
> Fix For: 0.6.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> After submitting the [PR #158|https://github.com/apache/nifi-minifi/pull/158]
> for a broken test (and underlying class) I realized the build breaks for an
> unrelated reason. The reason was {{commons-daemon}} version 1.1.0 being used
> which is not available on the
> [mirror|https://apache.claz.org/commons/daemon/binaries/windows/] anymore.
> Currently, there's only one, newer version 1.2.0 hosted on the mirror that
> should be used instead.
> Because of this issue with the build system it's not possible to submit any
> correct PRs at the moment, so I've set the priority to Blocker.
> This Jira issue is FYI as another PR to upgrade {{commons-deamon}} to 1.2.0
> is coming right up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINIFI-504) Upgrade commons-deamon to 1.2.0 to make build green again
[
https://issues.apache.org/jira/browse/MINIFI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881315#comment-16881315
]
Aldrin Piri commented on MINIFI-504:
[~shonzilla] Thanks for submitting this. The release happened quite recently
and did not go detected as early thanks to the US holiday. Have some logistics
to work out but should be taken care of shortly.
> Upgrade commons-deamon to 1.2.0 to make build green again
> -
>
> Key: MINIFI-504
> URL: https://issues.apache.org/jira/browse/MINIFI-504
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.6.0
>Reporter: Nenad Nikolic
>Priority: Blocker
> Fix For: 0.6.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After submitting the [PR #158|https://github.com/apache/nifi-minifi/pull/158]
> for a broken test (and underlying class) I realized the build breaks for an
> unrelated reason. The reason was {{commons-daemon}} version 1.1.0 being used
> which is not available on the
> [mirror|https://apache.claz.org/commons/daemon/binaries/windows/] anymore.
> Currently, there's only one, newer version 1.2.0 hosted on the mirror that
> should be used instead.
> Because of this issue with the build system it's not possible to submit any
> correct PRs at the moment, so I've set the priority to Blocker.
> This Jira issue is FYI as another PR to upgrade {{commons-deamon}} to 1.2.0
> is coming right up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (MINIFI-504) Upgrade commons-deamon to 1.2.0 to make build green again
[
https://issues.apache.org/jira/browse/MINIFI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri resolved MINIFI-504.
Resolution: Duplicate
> Upgrade commons-deamon to 1.2.0 to make build green again
> -
>
> Key: MINIFI-504
> URL: https://issues.apache.org/jira/browse/MINIFI-504
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.6.0
>Reporter: Nenad Nikolic
>Priority: Blocker
> Fix For: 0.6.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After submitting the [PR #158|https://github.com/apache/nifi-minifi/pull/158]
> for a broken test (and underlying class) I realized the build breaks for an
> unrelated reason. The reason was {{commons-daemon}} version 1.1.0 being used
> which is not available on the
> [mirror|https://apache.claz.org/commons/daemon/binaries/windows/] anymore.
> Currently, there's only one, newer version 1.2.0 hosted on the mirror that
> should be used instead.
> Because of this issue with the build system it's not possible to submit any
> correct PRs at the moment, so I've set the priority to Blocker.
> This Jira issue is FYI as another PR to upgrade {{commons-deamon}} to 1.2.0
> is coming right up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MINIFI-503) Update commons-daemon to 1.2
[ https://issues.apache.org/jira/browse/MINIFI-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-503: --- Fix Version/s: 0.6.0 > Update commons-daemon to 1.2 > > > Key: MINIFI-503 > URL: https://issues.apache.org/jira/browse/MINIFI-503 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Commons daemon recently released 1.2 which is causing builds to break as 1.1 > is no longer available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-503) Update commons-daemon to 1.2
Aldrin Piri created MINIFI-503: -- Summary: Update commons-daemon to 1.2 Key: MINIFI-503 URL: https://issues.apache.org/jira/browse/MINIFI-503 Project: Apache NiFi MiNiFi Issue Type: Task Components: Build Reporter: Aldrin Piri Assignee: Aldrin Piri Commons daemon recently released 1.2 which is causing builds to break as 1.1 is no longer available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-498) C2 Server Error - Too Many Open Files
[
https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880668#comment-16880668
]
Aldrin Piri commented on MINIFI-498:
[~Pverardi] Will revisit. Was out on vacation but was having problems
recreating initially.
Might you be able to grab a few bits of diagnostics when you experience the
issue? I would request:
* {{lsof -p }}
* {{jstack > jstack}}
* {{jmap -dump:file=/c2-heap-dump.bin }}
where PID is the id of the C2 process. This can be found via {{jps | grep
JettyServer | awk '{print $1}'}}
> C2 Server Error - Too Many Open Files
> -
>
> Key: MINIFI-498
> URL: https://issues.apache.org/jira/browse/MINIFI-498
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Command and Control
>Affects Versions: 0.5.0
> Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64)
> Java: 1.8.0_191-b12
> ulimits:
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 31769
> max locked memory (kbytes, -l) 64
> max memory size (kbytes, -m) unlimited
> open files (-n) 5
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) 1
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>Reporter: Michael
>Assignee: Aldrin Piri
>Priority: Blocker
> Fix For: 0.6.0
>
>
> After several days of running C2 the errors are being logged about having
> "Too Many Open Files". At this point, C2 is not responsive to clients trying
> to check for new configurations.
> _33e79e: Too many open files_
> _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by:
> java.nio.file.FileSystemException:
> /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_
>
> Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi
> instances are checking for new files every few seconds (probably too short),
> but it seems like maybe some file handles are not being cleaned up.
> Restarting C2 clears up this condition and C2 becomes responsive again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MINIFI-498) C2 Server Error - Too Many Open Files
[
https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880668#comment-16880668
]
Aldrin Piri edited comment on MINIFI-498 at 7/8/19 7:52 PM:
[~Pverardi] Will revisit. Was out on vacation but was having problems
recreating initially.
Might you be able to grab a few bits of diagnostics when you experience the
issue? I would request:
* {{lsof -p }}
* {{jstack > jstack}}
* {{jmap -dump:file=/c2-heap-dump.bin }}
where PID is the id of the C2 process. This can be found via {{jps | grep
JettyServer | awk '\{print $1\}'}}
was (Author: aldrin):
[~Pverardi] Will revisit. Was out on vacation but was having problems
recreating initially.
Might you be able to grab a few bits of diagnostics when you experience the
issue? I would request:
* {{lsof -p }}
* {{jstack > jstack}}
* {{jmap -dump:file=/c2-heap-dump.bin }}
where PID is the id of the C2 process. This can be found via {{jps | grep
JettyServer | awk '{print $1}'}}
> C2 Server Error - Too Many Open Files
> -
>
> Key: MINIFI-498
> URL: https://issues.apache.org/jira/browse/MINIFI-498
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Command and Control
>Affects Versions: 0.5.0
> Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64)
> Java: 1.8.0_191-b12
> ulimits:
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 31769
> max locked memory (kbytes, -l) 64
> max memory size (kbytes, -m) unlimited
> open files (-n) 5
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) 1
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>Reporter: Michael
>Assignee: Aldrin Piri
>Priority: Blocker
> Fix For: 0.6.0
>
>
> After several days of running C2 the errors are being logged about having
> "Too Many Open Files". At this point, C2 is not responsive to clients trying
> to check for new configurations.
> _33e79e: Too many open files_
> _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by:
> java.nio.file.FileSystemException:
> /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_
>
> Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi
> instances are checking for new files every few seconds (probably too short),
> but it seems like maybe some file handles are not being cleaned up.
> Restarting C2 clears up this condition and C2 becomes responsive again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MINIFI-501) Allow specification of an SSL Context/properties outside of the config.yml
Aldrin Piri created MINIFI-501: -- Summary: Allow specification of an SSL Context/properties outside of the config.yml Key: MINIFI-501 URL: https://issues.apache.org/jira/browse/MINIFI-501 Project: Apache NiFi MiNiFi Issue Type: Improvement Components: Agent Configuration/Installation Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.6.0 With the typical exchange of flows as through the config change notifiers, it can be unreasonable to expect that all properties would also be made available to allow for securing things like site to site which are defined/handled in nifi.properties in NiFi. We should allow the provisioning of a context through bootstrap.conf to allow the config.yml to focus more on the processing aspects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-499) Evaluate dependency sources
Aldrin Piri created MINIFI-499: -- Summary: Evaluate dependency sources Key: MINIFI-499 URL: https://issues.apache.org/jira/browse/MINIFI-499 Project: Apache NiFi MiNiFi Issue Type: Improvement Reporter: Aldrin Piri Assignee: Aldrin Piri As in NIFI-6323, performing a review of all dependency sources and upgrading references to HTTPS where possible/applicable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-162) Capture enhanced build information
[ https://issues.apache.org/jira/browse/MINIFI-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853020#comment-16853020 ] Aldrin Piri commented on MINIFI-162: Preference would be to capture and expose this in a separate file in lieu of cluttering configuration files. > Capture enhanced build information > -- > > Key: MINIFI-162 > URL: https://issues.apache.org/jira/browse/MINIFI-162 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > Work was done for NiFi (NIFI-2215) to expose additional information in the > About box. While we do not have a graphical view, capturing this information > in the minifi.properties file would be helpful for debugging and general > awareness of the system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFI-162) Capture enhanced build information
[ https://issues.apache.org/jira/browse/MINIFI-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-162: --- Summary: Capture enhanced build information (was: Capture enhanced build information in minifi.properties) > Capture enhanced build information > -- > > Key: MINIFI-162 > URL: https://issues.apache.org/jira/browse/MINIFI-162 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > Work was done for NiFi (NIFI-2215) to expose additional information in the > About box. While we do not have a graphical view, capturing this information > in the minifi.properties file would be helpful for debugging and general > awareness of the system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-162) Capture enhanced build information in minifi.properties
[ https://issues.apache.org/jira/browse/MINIFI-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-162: -- Assignee: Aldrin Piri > Capture enhanced build information in minifi.properties > --- > > Key: MINIFI-162 > URL: https://issues.apache.org/jira/browse/MINIFI-162 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > Work was done for NiFi (NIFI-2215) to expose additional information in the > About box. While we do not have a graphical view, capturing this information > in the minifi.properties file would be helpful for debugging and general > awareness of the system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-437) Convert Docker integration tests to make use of NiFi image
[ https://issues.apache.org/jira/browse/MINIFI-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16842352#comment-16842352 ] Aldrin Piri commented on MINIFI-437: Have used that elsewhere and might be a good fit. Mostly the tests currently have a dummy server that is mocking the interactions with nifi, so even using the raw image would be a nice improvement. > Convert Docker integration tests to make use of NiFi image > -- > > Key: MINIFI-437 > URL: https://issues.apache.org/jira/browse/MINIFI-437 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Docker >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > > Currently integration tests make use of a Mock NiFi server. With the > availability of the NiFi docker image, it would be helpful to use this to > verify full integration and expected behavior with respect to a NiFi RPG > target -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-437) Convert Docker integration tests to make use of NiFi image
[ https://issues.apache.org/jira/browse/MINIFI-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-437: -- Assignee: Aldrin Piri > Convert Docker integration tests to make use of NiFi image > -- > > Key: MINIFI-437 > URL: https://issues.apache.org/jira/browse/MINIFI-437 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Docker >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > > Currently integration tests make use of a Mock NiFi server. With the > availability of the NiFi docker image, it would be helpful to use this to > verify full integration and expected behavior with respect to a NiFi RPG > target -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840669#comment-16840669 ] Aldrin Piri commented on MINIFI-498: [~Pverardi], Thank you for the additional details. My recreation environment was only using 4 but certainly seems related in terms of how that would be accessed. Could you also specify if and how frequently the associated config files were modified in that time window? > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-422) Incorporate MiNiFi Java functionality as a specialized assembly of NiFI
[ https://issues.apache.org/jira/browse/MINIFI-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834758#comment-16834758 ] Aldrin Piri commented on MINIFI-422: Hi [~JPercivall]! I have a few branches that are working on aspects of this that I haven't been able to fully get instrumented with tests and such in NiFi. These are https://github.com/apiri/incubator-nifi/commits/MINIFI-488 & https://github.com/apiri/incubator-nifi/commits/MINIFI-485. MINIFI-488 a proof of concept startup of NiFi from a YAML config and certainly needs some adjustment but covers the base approach to make it work. My mental model is to incorporate some of the outstanding items into MiNiFi for one more release (although based on 1.8.x given the difficulties highlighted in 494) and work on some modularity to better compose items to port over to NiFi. At that point, update perform the transition targeting 1.10 carrying out the list of tasks encompassed in this ticket. If you are interested in getting involved in any of these steps let me know and am happy to collaborate to move things ahead a bit more. Have been a bit busy with other tasking and items. > Incorporate MiNiFi Java functionality as a specialized assembly of NiFI > > > Key: MINIFI-422 > URL: https://issues.apache.org/jira/browse/MINIFI-422 > Project: Apache NiFi MiNiFi > Issue Type: Task >Reporter: Aldrin Piri >Priority: Major > > At its core the Java implementation of MiNiFi has largely been a core body of > NiFi core libraries in a separate assembly with some additional extension > points, namely those of configuration (via YAML) and configuration change > listeners. > Due to working with some of the internals of NiFi that are not exactly meant > for external consumption, there has been a certain impedance with each > successive release to make use of the latest and greatest. > This ticket is to investigate and consider the incorporation of MiNiFi Java > into the NiFi code base in a manner as highlighted above, extending/adapting > the core libraries, providing some additional extension points, and then > generating a custom assembly. > The idea is that in lieu of duplicating bits of code and providing > workarounds around some of the internal APIs we can have a more streamlined > build and keep these items in lockstep with the core NiFi libraries being > more aware of changes that MiNiFi is inherently dependent upon. > To our users, there should be little perceptible change. The core means of > interaction should remain while providing a similar footprint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834112#comment-16834112 ] Aldrin Piri edited comment on MINIFI-498 at 5/6/19 7:21 PM: Hi [~mikenac]! I setup a test environment to try to draw this out over a longer term. Was there a typical time to failure? How many instances were configured? How many unique classes? Nothing is immediately jumping out at me in the profiler with a rather aggressive pull period (500 ms). *edit* I see that I overlooked that it was several days. Would be interested in the other numbers if available. was (Author: aldrin): Hi [~mikenac]! I setup a test environment to try to draw this out over a longer term. Was there a typical time to failure? How many instances were configured? How many unique classes? Nothing is immediately jumping out at me in the profiler with a rather aggressive pull period (500 ms). > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834112#comment-16834112 ] Aldrin Piri commented on MINIFI-498: Hi [~mikenac]! I setup a test environment to try to draw this out over a longer term. Was there a typical time to failure? How many instances were configured? How many unique classes? Nothing is immediately jumping out at me in the profiler with a rather aggressive pull period (500 ms). > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-498: --- Fix Version/s: 0.6.0 > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Priority: Major > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-498: -- Assignee: Aldrin Piri > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-498: --- Priority: Blocker (was: Major) > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Priority: Blocker > Fix For: 0.6.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFI-497) С2 Server: wrong regex pattern in "getConfiguration" (NiFiRestConfigurationProvider.java)
[
https://issues.apache.org/jira/browse/MINIFI-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri resolved MINIFI-497.
Resolution: Fixed
Fix Version/s: 0.6.0
> С2 Server: wrong regex pattern in "getConfiguration"
> (NiFiRestConfigurationProvider.java)
> -
>
> Key: MINIFI-497
> URL: https://issues.apache.org/jira/browse/MINIFI-497
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Command and Control
>Affects Versions: 0.5.0
>Reporter: Vladimir Mikhailov
>Assignee: Vladimir Mikhailov
>Priority: Critical
> Labels: easyfix
> Fix For: 0.6.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> C2 Server can't get from NiFi templates with versions v10+, only v1-v9.
> The reason is an error in the "getConfiguration" function, where
> "filenamePattern" is determined.
> Wrong code (maybe a typo?):
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9+])"));
> {code}
> It should be:
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9]+)"));
> {code}
> {code:java}
> [0-9+] -> [0-9]+{code}
> Link to source code:
> https://github.com/apache/nifi-minifi/blob/master/minifi-c2/minifi-c2-provider/minifi-c2-provider-nifi-rest/src/main/java/org/apache/nifi/minifi/c2/provider/nifi/rest/NiFiRestConfigurationProvider.java#L105
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINIFI-497) С2 Server: wrong regex pattern in "getConfiguration" (NiFiRestConfigurationProvider.java)
[
https://issues.apache.org/jira/browse/MINIFI-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802812#comment-16802812
]
Aldrin Piri commented on MINIFI-497:
[~VladimirMikhailov] Sounds great. I'll keep an eye out for your PR. Let me
know if I can be of assistance. I'll make sure you're a contributor to the
project so you can self assign.
Thanks!
> С2 Server: wrong regex pattern in "getConfiguration"
> (NiFiRestConfigurationProvider.java)
> -
>
> Key: MINIFI-497
> URL: https://issues.apache.org/jira/browse/MINIFI-497
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Command and Control
>Affects Versions: 0.5.0
>Reporter: Vladimir Mikhailov
>Priority: Critical
> Labels: easyfix
>
> C2 Server can't get from NiFi templates with versions v10+, only v1-v9.
> The reason is an error in the "getConfiguration" function, where
> "filenamePattern" is determined.
> Wrong code (maybe a typo?):
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9+])"));
> {code}
> It should be:
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9]+)"));
> {code}
> {code:java}
> [0-9+] -> [0-9]+{code}
> Link to source code:
> https://github.com/apache/nifi-minifi/blob/master/minifi-c2/minifi-c2-provider/minifi-c2-provider-nifi-rest/src/main/java/org/apache/nifi/minifi/c2/provider/nifi/rest/NiFiRestConfigurationProvider.java#L105
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINIFI-497) С2 Server: wrong regex pattern in "getConfiguration" (NiFiRestConfigurationProvider.java)
[
https://issues.apache.org/jira/browse/MINIFI-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802782#comment-16802782
]
Aldrin Piri commented on MINIFI-497:
Hey [~VladimirMikhailov],
Thanks for reporting. Was this something you were interested in tackling and
submitting a change for?
> С2 Server: wrong regex pattern in "getConfiguration"
> (NiFiRestConfigurationProvider.java)
> -
>
> Key: MINIFI-497
> URL: https://issues.apache.org/jira/browse/MINIFI-497
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Command and Control
>Affects Versions: 0.5.0
>Reporter: Vladimir Mikhailov
>Priority: Critical
> Labels: easyfix
>
> C2 Server can't get from NiFi templates with versions v10+, only v1-v9.
> The reason is an error in the "getConfiguration" function, where
> "filenamePattern" is determined.
> Wrong code (maybe a typo?):
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9+])"));
> {code}
> It should be:
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9]+)"));
> {code}
> {code:java}
> [0-9+] -> [0-9]+{code}
> Link to source code:
> https://github.com/apache/nifi-minifi/blob/master/minifi-c2/minifi-c2-provider/minifi-c2-provider-nifi-rest/src/main/java/org/apache/nifi/minifi/c2/provider/nifi/rest/NiFiRestConfigurationProvider.java#L105
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MINIFI-496) Multiple RPGs to the same NiFi instance will preclude successful transformation
[ https://issues.apache.org/jira/browse/MINIFI-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-496: -- Assignee: Aldrin Piri > Multiple RPGs to the same NiFi instance will preclude successful > transformation > --- > > Key: MINIFI-496 > URL: https://issues.apache.org/jira/browse/MINIFI-496 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Processing Configuration >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > > If a template references the same NiFi instance within more than one RPGs, > the transformer will be nonplussed over the reuse of a unique id. While we > need certain unique constraints for components, this is a special case that > needs separate handling. Will supply a template that exhibits this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-496) Multiple RPGs to the same NiFi instance will preclude successful transformation
Aldrin Piri created MINIFI-496: -- Summary: Multiple RPGs to the same NiFi instance will preclude successful transformation Key: MINIFI-496 URL: https://issues.apache.org/jira/browse/MINIFI-496 Project: Apache NiFi MiNiFi Issue Type: Bug Components: Processing Configuration Reporter: Aldrin Piri Fix For: 0.6.0 If a template references the same NiFi instance within more than one RPGs, the transformer will be nonplussed over the reuse of a unique id. While we need certain unique constraints for components, this is a special case that needs separate handling. Will supply a template that exhibits this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-495) minifi-docker module should depend on minifi-assembly
[ https://issues.apache.org/jira/browse/MINIFI-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-495: -- Assignee: Aldrin Piri > minifi-docker module should depend on minifi-assembly > - > > Key: MINIFI-495 > URL: https://issues.apache.org/jira/browse/MINIFI-495 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Docker >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.5.0 > > > Currently the docker module does not depend on the assembly. This means that > for multhreaded builds there is a potential that the docker build will make > use of what is a stale assembly. Or, for a clean state, will not be able to > build when activated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Moved] (MINIFI-495) minifi-docker module should depend on minifi-assembly
[ https://issues.apache.org/jira/browse/MINIFI-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri moved NIFI-6133 to MINIFI-495: -- Fix Version/s: (was: 0.5.0) 0.5.0 Component/s: (was: Tools and Build) (was: Docker) Docker Key: MINIFI-495 (was: NIFI-6133) Project: Apache NiFi MiNiFi (was: Apache NiFi) > minifi-docker module should depend on minifi-assembly > - > > Key: MINIFI-495 > URL: https://issues.apache.org/jira/browse/MINIFI-495 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Docker >Reporter: Aldrin Piri >Priority: Major > Fix For: 0.5.0 > > > Currently the docker module does not depend on the assembly. This means that > for multhreaded builds there is a potential that the docker build will make > use of what is a stale assembly. Or, for a clean state, will not be able to > build when activated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-494) Update NiFi dependency to 1.9.0
[ https://issues.apache.org/jira/browse/MINIFI-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781079#comment-16781079 ] Aldrin Piri commented on MINIFI-494: [~jzemerick] Yeah, understand the issue about the possible baggage, however I think the full incorporation is the best course. In that scenario, folks that are also MiNiFi devs can be NiFi devs, too. Realistically MiNiFi is just a specialized assembly with a few items filtered out. I've made some nice progress that I intend to get back to shortly porting all the features over into the NiFi codebase (like launching a NiFi flow from YAML) > Update NiFi dependency to 1.9.0 > --- > > Key: MINIFI-494 > URL: https://issues.apache.org/jira/browse/MINIFI-494 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Affects Versions: 0.6.0 >Reporter: Jeff Zemerick >Priority: Major > > Update NiFi dependency to 1.9.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-494) Update NiFi dependency to 1.9.0
[ https://issues.apache.org/jira/browse/MINIFI-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780601#comment-16780601 ] Aldrin Piri commented on MINIFI-494: Hey [~jzemerick], I may be mistaken (and would love if I was) but I think the issue will rear its head when you start running it. The classpath issues will be the mess to untangle and are not straightforward. > Update NiFi dependency to 1.9.0 > --- > > Key: MINIFI-494 > URL: https://issues.apache.org/jira/browse/MINIFI-494 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Affects Versions: 0.6.0 >Reporter: Jeff Zemerick >Assignee: Jeff Zemerick >Priority: Major > > Update NiFi dependency to 1.9.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-494) Update NiFi dependency to 1.9.0
[ https://issues.apache.org/jira/browse/MINIFI-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16779710#comment-16779710 ] Aldrin Piri commented on MINIFI-494: Hey [~jzemerick], As a bit of a warning, this is not straightforward. There was some usage of internal framework APIs that have changed to support all the great nar loading functionalities. In my mind, this seemed to up the importance of MINIFI-422. Happy to scope out things if you are able to reason about it and get it working and collab along the way, but my initial inspections were not overly fruitful without mass changes. > Update NiFi dependency to 1.9.0 > --- > > Key: MINIFI-494 > URL: https://issues.apache.org/jira/browse/MINIFI-494 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Affects Versions: 0.6.0 >Reporter: Jeff Zemerick >Assignee: Jeff Zemerick >Priority: Major > > Update NiFi dependency to 1.9.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFI-493) NPE when converting old templates using toolkit
[ https://issues.apache.org/jira/browse/MINIFI-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFI-493. Resolution: Fixed > NPE when converting old templates using toolkit > --- > > Key: MINIFI-493 > URL: https://issues.apache.org/jira/browse/MINIFI-493 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Our handling of the changes to RPG ids uses a switch on a given encoding > version. Older versions of NiFi (verified with 0.4.0) do not provide this. > Accordingly, there is no reason why we cannot also convert older templates. > Some simple null guarding will allow us to treat older versions as the base > case where RPG IDs are treated the same as those encodings < 1.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFI-493) NPE when converting old templates using toolkit
[ https://issues.apache.org/jira/browse/MINIFI-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-493: --- Description: Our handling of the changes to RPG ids uses a switch on a given encoding version. Older versions of NiFi (verified with 0.4.0) do not provide this. Accordingly, there is no reason why we cannot also convert older templates. Some simple null guarding will allow us to treat older versions as the base case where RPG IDs are treated the same as those encodings < 1.2 > NPE when converting old templates using toolkit > --- > > Key: MINIFI-493 > URL: https://issues.apache.org/jira/browse/MINIFI-493 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > > Our handling of the changes to RPG ids uses a switch on a given encoding > version. Older versions of NiFi (verified with 0.4.0) do not provide this. > Accordingly, there is no reason why we cannot also convert older templates. > Some simple null guarding will allow us to treat older versions as the base > case where RPG IDs are treated the same as those encodings < 1.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-493) NPE when converting old templates using toolkit
[ https://issues.apache.org/jira/browse/MINIFI-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-493: -- Assignee: Aldrin Piri > NPE when converting old templates using toolkit > --- > > Key: MINIFI-493 > URL: https://issues.apache.org/jira/browse/MINIFI-493 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.6.0 > > > Our handling of the changes to RPG ids uses a switch on a given encoding > version. Older versions of NiFi (verified with 0.4.0) do not provide this. > Accordingly, there is no reason why we cannot also convert older templates. > Some simple null guarding will allow us to treat older versions as the base > case where RPG IDs are treated the same as those encodings < 1.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-493) NPE when converting old templates using toolkit
Aldrin Piri created MINIFI-493: -- Summary: NPE when converting old templates using toolkit Key: MINIFI-493 URL: https://issues.apache.org/jira/browse/MINIFI-493 Project: Apache NiFi MiNiFi Issue Type: Bug Reporter: Aldrin Piri Fix For: 0.6.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-478) OrderedPropertiesTest fails on Java 11 / OS X
[ https://issues.apache.org/jira/browse/MINIFI-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-478: -- Assignee: (was: Aldrin Piri) > OrderedPropertiesTest fails on Java 11 / OS X > - > > Key: MINIFI-478 > URL: https://issues.apache.org/jira/browse/MINIFI-478 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Dustin Rodrigues >Priority: Major > > When running on OS X 10.14 ( Mojave ) with openjdk 11, the > OrderedPropertiesTest is failing. When using jdk1.8.0_192 instead, the test > succeeds. > > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.05 sec <<< > FAILURE! - in org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest > testOrderedProperties(org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest) > Time elapsed: 0.05 sec <<< FAILURE! > org.junit.ComparisonFailure: expected:<[prop1=newVal1]> but was:<[#this is > property 2]> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest.testOrderedProperties(OrderedPropertiesTest.java:49) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-487) Support change ingestors
[ https://issues.apache.org/jira/browse/MINIFI-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-487: -- Assignee: Aldrin Piri > Support change ingestors > > > Key: MINIFI-487 > URL: https://issues.apache.org/jira/browse/MINIFI-487 > Project: Apache NiFi MiNiFi > Issue Type: Sub-task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFI-492) Evaluate/convert to Jackson YAML
[ https://issues.apache.org/jira/browse/MINIFI-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720536#comment-16720536 ] Aldrin Piri commented on MINIFI-492: https://github.com/FasterXML/jackson-dataformats-text/tree/master/yaml > Evaluate/convert to Jackson YAML > > > Key: MINIFI-492 > URL: https://issues.apache.org/jira/browse/MINIFI-492 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Processing Configuration >Reporter: Aldrin Piri >Priority: Minor > > Jackson appears to have a YAML module. This may allow us to reduce some of > our code footprint in handling the minifi configuration files and more easily > map to NiFi components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFI-492) Evaluate/convert to Jackson YAML
[ https://issues.apache.org/jira/browse/MINIFI-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-492: --- Priority: Minor (was: Major) > Evaluate/convert to Jackson YAML > > > Key: MINIFI-492 > URL: https://issues.apache.org/jira/browse/MINIFI-492 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Processing Configuration >Reporter: Aldrin Piri >Priority: Minor > > Jackson appears to have a YAML module. This may allow us to reduce some of > our code footprint in handling the minifi configuration files and more easily > map to NiFi components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-492) Evaluate/convert to Jackson YAML
Aldrin Piri created MINIFI-492: -- Summary: Evaluate/convert to Jackson YAML Key: MINIFI-492 URL: https://issues.apache.org/jira/browse/MINIFI-492 Project: Apache NiFi MiNiFi Issue Type: Improvement Components: Processing Configuration Reporter: Aldrin Piri Jackson appears to have a YAML module. This may allow us to reduce some of our code footprint in handling the minifi configuration files and more easily map to NiFi components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MINIFI-488) Allow flow construction from YAML config
[ https://issues.apache.org/jira/browse/MINIFI-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned MINIFI-488: -- Assignee: Aldrin Piri > Allow flow construction from YAML config > > > Key: MINIFI-488 > URL: https://issues.apache.org/jira/browse/MINIFI-488 > Project: Apache NiFi MiNiFi > Issue Type: Sub-task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFI-482) MiNiFi handle multiple NiFi urls in RPG
[ https://issues.apache.org/jira/browse/MINIFI-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFI-482: --- Fix Version/s: 0.6.0 > MiNiFi handle multiple NiFi urls in RPG > --- > > Key: MINIFI-482 > URL: https://issues.apache.org/jira/browse/MINIFI-482 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Neha Bathra >Assignee: Aldrin Piri >Priority: Critical > Fix For: 0.6.0 > > > For an RPG, when multiple comma separated nifi urls are configured, only the > first url is considered for data flow. In case, the first url is down, it > should be tried on the other nodes. Currently, the data flow gets stuck when > the first nifi url is down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-490) Generically support reporting tasks
Aldrin Piri created MINIFI-490: -- Summary: Generically support reporting tasks Key: MINIFI-490 URL: https://issues.apache.org/jira/browse/MINIFI-490 Project: Apache NiFi MiNiFi Issue Type: Improvement Reporter: Aldrin Piri -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-491) Add a Site to Site periodic status reporter implementation
Aldrin Piri created MINIFI-491: -- Summary: Add a Site to Site periodic status reporter implementation Key: MINIFI-491 URL: https://issues.apache.org/jira/browse/MINIFI-491 Project: Apache NiFi MiNiFi Issue Type: Improvement Reporter: Aldrin Piri -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-487) Support change ingestors
Aldrin Piri created MINIFI-487: -- Summary: Support change ingestors Key: MINIFI-487 URL: https://issues.apache.org/jira/browse/MINIFI-487 Project: Apache NiFi MiNiFi Issue Type: Sub-task Reporter: Aldrin Piri -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFI-488) Allow flow construction from YAML config
Aldrin Piri created MINIFI-488: -- Summary: Allow flow construction from YAML config Key: MINIFI-488 URL: https://issues.apache.org/jira/browse/MINIFI-488 Project: Apache NiFi MiNiFi Issue Type: Sub-task Reporter: Aldrin Piri -- This message was sent by Atlassian JIRA (v7.6.3#76005)
