[jira] [Created] (NIFI-2408) If a node is disconnected, it should still provide user ability to see the 'cluster screen'

Mark Payne created NIFI-2408: Summary: If a node is disconnected, it should still provide user ability to see the 'cluster screen' Key: NIFI-2408 URL: https://issues.apache.org/jira/browse/NIFI-2408

[jira] [Updated] (NIFI-2338) Replay Authorization Check happening twice

[ https://issues.apache.org/jira/browse/NIFI-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2338: - Resolution: Fixed Status: Resolved (was: Patch Available) > Replay Authorization Check happening

[jira] [Updated] (NIFI-2346) Add resource for authorizing all data access

[ https://issues.apache.org/jira/browse/NIFI-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2346: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add resource for authorizing all data

[jira] [Created] (NIFI-2244) Cannot modify connection if user does not have permissions to modify source or destination

Mark Payne created NIFI-2244: Summary: Cannot modify connection if user does not have permissions to modify source or destination Key: NIFI-2244 URL: https://issues.apache.org/jira/browse/NIFI-2244

[jira] [Resolved] (NIFI-2022) Update Site-to-Site Authorization Code

[ https://issues.apache.org/jira/browse/NIFI-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-2022. -- Resolution: Fixed > Update Site-to-Site Authorization Code > -- > >

[jira] [Created] (NIFI-2260) Unable to Replay / Download provenance events when clustered

Mark Payne created NIFI-2260: Summary: Unable to Replay / Download provenance events when clustered Key: NIFI-2260 URL: https://issues.apache.org/jira/browse/NIFI-2260 Project: Apache NiFi

[jira] [Updated] (NIFI-1157) Remove deprecated classes and methods

[ https://issues.apache.org/jira/browse/NIFI-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-1157: - Resolution: Fixed Status: Resolved (was: Patch Available) > Remove deprecated classes and methods

[jira] [Updated] (NIFI-2030) Refactor how HTTP-based Site-to-Site ports are communicated

[ https://issues.apache.org/jira/browse/NIFI-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2030: - Fix Version/s: (was: 1.0.0) > Refactor how HTTP-based Site-to-Site ports are communicated >

[jira] [Updated] (NIFI-2145) When saving flow, NiFi should allow the flow to automatically be backed up

[ https://issues.apache.org/jira/browse/NIFI-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2145: - Resolution: Fixed Status: Resolved (was: Patch Available) > When saving flow, NiFi should allow

[jira] [Updated] (NIFI-1307) Un-deprecate FlowFile.getId()

[ https://issues.apache.org/jira/browse/NIFI-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-1307: - Resolution: Fixed Status: Resolved (was: Patch Available) > Un-deprecate FlowFile.getId() >

[jira] [Resolved] (NIFI-2261) Enabling or Disabling Controller Service gives Parse Error in browser

[ https://issues.apache.org/jira/browse/NIFI-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-2261. -- Resolution: Fixed > Enabling or Disabling Controller Service gives Parse Error in browser >

[jira] [Updated] (NIFI-2238) Controller-Level bulletins no longer being shown in UI

[ https://issues.apache.org/jira/browse/NIFI-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2238: - Resolution: Fixed Status: Resolved (was: Patch Available) > Controller-Level bulletins no longer

[jira] [Updated] (NIFI-2204) Move Controller level bulletins out of Controller Status

[ https://issues.apache.org/jira/browse/NIFI-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2204: - Resolution: Fixed Status: Resolved (was: Patch Available) > Move Controller level bulletins out

[jira] [Updated] (NIFI-2292) Nodes in cluster sometimes become out-of-sync with actual 'connection state' of node

[ https://issues.apache.org/jira/browse/NIFI-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2292: - Status: Patch Available (was: Open) > Nodes in cluster sometimes become out-of-sync with actual

[jira] [Created] (NIFI-2353) When not clustered, nifi logs warning about not being able to find cluster coordinator

Mark Payne created NIFI-2353: Summary: When not clustered, nifi logs warning about not being able to find cluster coordinator Key: NIFI-2353 URL: https://issues.apache.org/jira/browse/NIFI-2353 Project:

[jira] [Commented] (NIFI-2362) BinFiles: incorrect error logging

[ https://issues.apache.org/jira/browse/NIFI-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389752#comment-15389752 ] Mark Payne commented on NIFI-2362: -- [~devriesb] both of the above log messages *should* produce the same

[jira] [Commented] (NIFI-2395) PersistentProvenanceRepository Deadlocks caused by a blocked journal merge

[ https://issues.apache.org/jira/browse/NIFI-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395784#comment-15395784 ] Mark Payne commented on NIFI-2395: -- If the thread that created the futures didn't get CPU time until after

[jira] [Commented] (NIFI-2395) PersistentProvenanceRepository Deadlocks caused by a blocked journal merge

[ https://issues.apache.org/jira/browse/NIFI-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395825#comment-15395825 ] Mark Payne commented on NIFI-2395: -- I certainly think it would be interesting to do that so that we can

[jira] [Commented] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[ https://issues.apache.org/jira/browse/NIFI-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395894#comment-15395894 ] Mark Payne commented on NIFI-2406: -- [~JPercivall] - thanks for reporting this! I have created a PR that I

[jira] [Updated] (NIFI-2406) Rare start-up problems resulting in all nodes disconnected

[ https://issues.apache.org/jira/browse/NIFI-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2406: - Status: Patch Available (was: Open) > Rare start-up problems resulting in all nodes disconnected >

[jira] [Updated] (NIFI-2388) NPE during validation of Controller Service that relies on another Controller Service at the controller level

[ https://issues.apache.org/jira/browse/NIFI-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2388: - Status: Patch Available (was: Open) > NPE during validation of Controller Service that relies on another

[jira] [Updated] (NIFI-2395) PersistentProvenanceRepository Deadlocks caused by a blocked journal merge

[ https://issues.apache.org/jira/browse/NIFI-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2395: - Status: Patch Available (was: Open) > PersistentProvenanceRepository Deadlocks caused by a blocked

[jira] [Created] (NIFI-2419) Node could be elected Cluster Coordinator when disconnected from cluster

Mark Payne created NIFI-2419: Summary: Node could be elected Cluster Coordinator when disconnected from cluster Key: NIFI-2419 URL: https://issues.apache.org/jira/browse/NIFI-2419 Project: Apache NiFi

[jira] [Updated] (NIFI-2337) IllegalMonitorStateException when disconnecting node

[ https://issues.apache.org/jira/browse/NIFI-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2337: - Status: Patch Available (was: Open) > IllegalMonitorStateException when disconnecting node >

[jira] [Updated] (NIFI-2419) Node could be elected Cluster Coordinator when disconnected from cluster

[ https://issues.apache.org/jira/browse/NIFI-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2419: - Status: Patch Available (was: In Progress) > Node could be elected Cluster Coordinator when disconnected

[jira] [Updated] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster

[ https://issues.apache.org/jira/browse/NIFI-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2305: - Status: Patch Available (was: Reopened) > Nodes run "Primary Node Only" processors when disconnected from

[jira] [Updated] (NIFI-2360) Improve robustness of cluster when relying on embedded zookeeper

[ https://issues.apache.org/jira/browse/NIFI-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2360: - Status: Patch Available (was: Open) > Improve robustness of cluster when relying on embedded zookeeper >

[jira] [Updated] (NIFI-2431) When a new node joins cluster, it can be elected Cluster Coordinator even if its flow is different than cluster's

[ https://issues.apache.org/jira/browse/NIFI-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2431: - Status: Patch Available (was: Open) > When a new node joins cluster, it can be elected Cluster

[jira] [Updated] (NIFI-2245) Summary Page: Node-wise break down incomplete

[ https://issues.apache.org/jira/browse/NIFI-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2245: - Resolution: Fixed Status: Resolved (was: Patch Available) > Summary Page: Node-wise break down

[jira] [Created] (NIFI-2436) When closing "View Stats" page, UI is no longer accessible

Mark Payne created NIFI-2436: Summary: When closing "View Stats" page, UI is no longer accessible Key: NIFI-2436 URL: https://issues.apache.org/jira/browse/NIFI-2436 Project: Apache NiFi Issue

[jira] [Created] (NIFI-2432) Clarify message provided when local flow differs from cluster flow

Mark Payne created NIFI-2432: Summary: Clarify message provided when local flow differs from cluster flow Key: NIFI-2432 URL: https://issues.apache.org/jira/browse/NIFI-2432 Project: Apache NiFi

[jira] [Updated] (NIFI-2291) Site-to-Site Provenance Reporting Task showing wrong content URI

[ https://issues.apache.org/jira/browse/NIFI-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2291: - Status: Patch Available (was: Open) > Site-to-Site Provenance Reporting Task showing wrong content URI >

[jira] [Assigned] (NIFI-2291) Site-to-Site Provenance Reporting Task showing wrong content URI

[ https://issues.apache.org/jira/browse/NIFI-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-2291: Assignee: Mark Payne > Site-to-Site Provenance Reporting Task showing wrong content URI >

[jira] [Created] (NIFI-2445) PublishKafka sends flowfiles to 'success' if not authorized to write to topic

Mark Payne created NIFI-2445: Summary: PublishKafka sends flowfiles to 'success' if not authorized to write to topic Key: NIFI-2445 URL: https://issues.apache.org/jira/browse/NIFI-2445 Project: Apache

[jira] [Commented] (NIFI-2445) PublishKafka sends flowfiles to 'success' if not authorized to write to topic

[ https://issues.apache.org/jira/browse/NIFI-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401986#comment-15401986 ] Mark Payne commented on NIFI-2445: -- I also see this happen when the topic that I attempt to send to does

[jira] [Created] (NIFI-2447) When calculating lineage for a FlowFile, should provide a mechanism for starting with a particular event instead of FlowFile UUID

Mark Payne created NIFI-2447: Summary: When calculating lineage for a FlowFile, should provide a mechanism for starting with a particular event instead of FlowFile UUID Key: NIFI-2447 URL:

[jira] [Created] (NIFI-2444) PublishKafka does not generate bulletins when there are problems

Mark Payne created NIFI-2444: Summary: PublishKafka does not generate bulletins when there are problems Key: NIFI-2444 URL: https://issues.apache.org/jira/browse/NIFI-2444 Project: Apache NiFi

[jira] [Commented] (NIFI-2395) PersistentProvenanceRepository Deadlocks caused by a blocked journal merge

[ https://issues.apache.org/jira/browse/NIFI-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395721#comment-15395721 ] Mark Payne commented on NIFI-2395: -- Brian - I have looked into this. I believe the condition in the while

[jira] [Assigned] (NIFI-2535) SSL context service property in Publish/ConsumeKafka is causing clustering issue

[ https://issues.apache.org/jira/browse/NIFI-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-2535: Assignee: Mark Payne > SSL context service property in Publish/ConsumeKafka is causing clustering

[jira] [Updated] (NIFI-2540) Templates should be scrubbed for Property Descriptors' descriptions

[ https://issues.apache.org/jira/browse/NIFI-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2540: - Status: Patch Available (was: Open) > Templates should be scrubbed for Property Descriptors' descriptions

[jira] [Created] (NIFI-2463) Improve error message for PublishKafka

Mark Payne created NIFI-2463: Summary: Improve error message for PublishKafka Key: NIFI-2463 URL: https://issues.apache.org/jira/browse/NIFI-2463 Project: Apache NiFi Issue Type: Improvement

[jira] [Updated] (NIFI-2452) Provenance Repository's Index Readers can be prematurely closed

[ https://issues.apache.org/jira/browse/NIFI-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2452: - Status: Patch Available (was: Open) > Provenance Repository's Index Readers can be prematurely closed >

[jira] [Resolved] (NIFI-2445) PublishKafka sends flowfiles to 'success' if not authorized to write to topic

[ https://issues.apache.org/jira/browse/NIFI-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-2445. -- Resolution: Fixed > PublishKafka sends flowfiles to 'success' if not authorized to write to topic >

[jira] [Resolved] (NIFI-2444) PublishKafka does not generate bulletins when there are problems

[ https://issues.apache.org/jira/browse/NIFI-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-2444. -- Resolution: Fixed > PublishKafka does not generate bulletins when there are problems >

[jira] [Created] (NIFI-2452) Provenance Repository's Index Readers can be prematurely closed

Mark Payne created NIFI-2452: Summary: Provenance Repository's Index Readers can be prematurely closed Key: NIFI-2452 URL: https://issues.apache.org/jira/browse/NIFI-2452 Project: Apache NiFi

[jira] [Created] (NIFI-2540) Templates should be scrubbed for Property Descriptors' descriptions

Mark Payne created NIFI-2540: Summary: Templates should be scrubbed for Property Descriptors' descriptions Key: NIFI-2540 URL: https://issues.apache.org/jira/browse/NIFI-2540 Project: Apache NiFi

[jira] [Assigned] (NIFI-2545) Cannot tell a processor is "STOPPING", can edit, cannot restart it

[ https://issues.apache.org/jira/browse/NIFI-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-2545: Assignee: Mark Payne > Cannot tell a processor is "STOPPING", can edit, cannot restart it >

[jira] [Commented] (NIFI-2545) Cannot tell a processor is "STOPPING", can edit, cannot restart it

[ https://issues.apache.org/jira/browse/NIFI-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417180#comment-15417180 ] Mark Payne commented on NIFI-2545: -- Yes - I believe all that you said here is accurate. > Cannot tell a

[jira] [Commented] (NIFI-2551) Rare condition causes FileSystemRepository NPE

[ https://issues.apache.org/jira/browse/NIFI-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417482#comment-15417482 ] Mark Payne commented on NIFI-2551: -- [~mosermw] - wow this is a great find! Greatly appreciate all of the

[jira] [Created] (NIFI-2544) Create integration tests for Zero-Master Clustering

Mark Payne created NIFI-2544: Summary: Create integration tests for Zero-Master Clustering Key: NIFI-2544 URL: https://issues.apache.org/jira/browse/NIFI-2544 Project: Apache NiFi Issue Type:

[jira] [Updated] (NIFI-2366) After creating a template, it errors out when trying to add it back

[ https://issues.apache.org/jira/browse/NIFI-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2366: - Resolution: Fixed Status: Resolved (was: Patch Available) > After creating a template, it errors

[jira] [Created] (NIFI-2466) SSLContextService should support specifying Key Password

Mark Payne created NIFI-2466: Summary: SSLContextService should support specifying Key Password Key: NIFI-2466 URL: https://issues.apache.org/jira/browse/NIFI-2466 Project: Apache NiFi Issue

[jira] [Updated] (NIFI-2466) SSLContextService should support specifying Key Password

[ https://issues.apache.org/jira/browse/NIFI-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2466: - Assignee: Mark Payne Status: Patch Available (was: Open) > SSLContextService should support

[jira] [Updated] (NIFI-2474) TestRunner should not expose a VariableRegistry construct

[ https://issues.apache.org/jira/browse/NIFI-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2474: - Assignee: Mark Payne Status: Patch Available (was: Open) > TestRunner should not expose a

[jira] [Updated] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ https://issues.apache.org/jira/browse/NIFI-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2423: - Attachment: 0001-NIFI-2423-Make-use-of-the-SSLContextService-to-provi.patch > Add a sensitive property to

[jira] [Created] (NIFI-2474) TestRunner should not expose a VariableRegistry construct

Mark Payne created NIFI-2474: Summary: TestRunner should not expose a VariableRegistry construct Key: NIFI-2474 URL: https://issues.apache.org/jira/browse/NIFI-2474 Project: Apache NiFi Issue

[jira] [Updated] (NIFI-2391) Add toString() implementation to ComponentDTO

[ https://issues.apache.org/jira/browse/NIFI-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2391: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add toString() implementation to

[jira] [Commented] (NIFI-2458) After canceling provenance query, cannot submit a new one

[ https://issues.apache.org/jira/browse/NIFI-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406453#comment-15406453 ] Mark Payne commented on NIFI-2458: -- So the interesting bit here is that we have optimized the query so

[jira] [Updated] (NIFI-2291) Site-to-Site Provenance Reporting Task showing wrong content URI

[ https://issues.apache.org/jira/browse/NIFI-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2291: - Resolution: Fixed Status: Resolved (was: Patch Available) > Site-to-Site Provenance Reporting

[jira] [Updated] (NIFI-2478) Can not use the same Zookeeper by multiple NiFi clusters

[ https://issues.apache.org/jira/browse/NIFI-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2478: - Priority: Blocker (was: Major) > Can not use the same Zookeeper by multiple NiFi clusters >

[jira] [Assigned] (NIFI-2478) Can not use the same Zookeeper by multiple NiFi clusters

[ https://issues.apache.org/jira/browse/NIFI-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-2478: Assignee: Mark Payne > Can not use the same Zookeeper by multiple NiFi clusters >

[jira] [Updated] (NIFI-2478) Can not use the same Zookeeper by multiple NiFi clusters

[ https://issues.apache.org/jira/browse/NIFI-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2478: - Fix Version/s: 1.0.0 > Can not use the same Zookeeper by multiple NiFi clusters >

[jira] [Resolved] (NIFI-2478) Can not use the same Zookeeper by multiple NiFi clusters

[ https://issues.apache.org/jira/browse/NIFI-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-2478. -- Resolution: Fixed > Can not use the same Zookeeper by multiple NiFi clusters >

[jira] [Commented] (NIFI-2478) Can not use the same Zookeeper by multiple NiFi clusters

[ https://issues.apache.org/jira/browse/NIFI-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407639#comment-15407639 ] Mark Payne commented on NIFI-2478: -- [~ijokarumawak] - great catch! Excellent analysis - you are absolutely

[jira] [Updated] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ https://issues.apache.org/jira/browse/NIFI-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2423: - Attachment: (was: 0001-NIFI-2423-Make-use-of-the-SSLContextService-to-provi.patch) > Add a sensitive

[jira] [Commented] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ https://issues.apache.org/jira/browse/NIFI-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407651#comment-15407651 ] Mark Payne commented on NIFI-2423: -- I replaced the patch with a new one that takes advantage of the

[jira] [Updated] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ https://issues.apache.org/jira/browse/NIFI-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2423: - Attachment: 0001-NIFI-2423-Make-use-of-the-SSLContextService-to-provi.patch > Add a sensitive property to

[jira] [Created] (NIFI-2483) Remove "Passthrough" relationship of GetHDFS

Mark Payne created NIFI-2483: Summary: Remove "Passthrough" relationship of GetHDFS Key: NIFI-2483 URL: https://issues.apache.org/jira/browse/NIFI-2483 Project: Apache NiFi Issue Type: Task

[jira] [Updated] (NIFI-2419) Node could be elected Cluster Coordinator when disconnected from cluster

[ https://issues.apache.org/jira/browse/NIFI-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2419: - Resolution: Fixed Status: Resolved (was: Patch Available) > Node could be elected Cluster

[jira] [Updated] (NIFI-1870) Restore go to source/destination capability

[ https://issues.apache.org/jira/browse/NIFI-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-1870: - Issue Type: Task (was: Sub-task) Parent: (was: NIFI-1550) > Restore go to source/destination

[jira] [Updated] (NIFI-2472) Copy and Pasting groups of components repositions them erratically

[ https://issues.apache.org/jira/browse/NIFI-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2472: - Priority: Blocker (was: Major) > Copy and Pasting groups of components repositions them erratically >

[jira] [Assigned] (NIFI-2472) Copy and Pasting groups of components repositions them erratically

[ https://issues.apache.org/jira/browse/NIFI-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-2472: Assignee: Mark Payne > Copy and Pasting groups of components repositions them erratically >

[jira] [Updated] (NIFI-2483) Remove "Passthrough" relationship of GetHDFS

[ https://issues.apache.org/jira/browse/NIFI-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2483: - Status: Patch Available (was: Open) > Remove "Passthrough" relationship of GetHDFS >

[jira] [Updated] (NIFI-2474) TestRunner should not expose a VariableRegistry construct

[ https://issues.apache.org/jira/browse/NIFI-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2474: - Resolution: Fixed Status: Resolved (was: Patch Available) > TestRunner should not expose a

[jira] [Commented] (NIFI-2551) Rare condition causes FileSystemRepository NPE

[ https://issues.apache.org/jira/browse/NIFI-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418871#comment-15418871 ] Mark Payne commented on NIFI-2551: -- [~mosermw] - The good news is that I am to very easily reproduce this

[jira] [Commented] (NIFI-2551) Rare condition causes FileSystemRepository NPE

[ https://issues.apache.org/jira/browse/NIFI-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418984#comment-15418984 ] Mark Payne commented on NIFI-2551: -- [~mosermw] - I hear ya - this part of the code base is far from

[jira] [Created] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

Mark Payne created NIFI-2566: Summary: Clustered Nodes can become out of sync regarding which node is coordinator Key: NIFI-2566 URL: https://issues.apache.org/jira/browse/NIFI-2566 Project: Apache NiFi

[jira] [Updated] (NIFI-2535) SSL context service property in Publish/ConsumeKafka is causing clustering issue

[ https://issues.apache.org/jira/browse/NIFI-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2535: - Status: Patch Available (was: Open) > SSL context service property in Publish/ConsumeKafka is causing

[jira] [Commented] (NIFI-2551) Rare condition causes FileSystemRepository NPE

[ https://issues.apache.org/jira/browse/NIFI-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419215#comment-15419215 ] Mark Payne commented on NIFI-2551: -- [~mosermw] i have posted a path. Please check it out when you get a

[jira] [Updated] (NIFI-2551) Rare condition causes FileSystemRepository NPE

[ https://issues.apache.org/jira/browse/NIFI-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2551: - Fix Version/s: 0.8.0 1.0.0 > Rare condition causes FileSystemRepository NPE >

[jira] [Created] (NIFI-2333) When a flow consists only of controller-level reporting tasks/controller services, nodes cannot rejoin cluster once they have disconnected

Mark Payne created NIFI-2333: Summary: When a flow consists only of controller-level reporting tasks/controller services, nodes cannot rejoin cluster once they have disconnected Key: NIFI-2333 URL:

[jira] [Created] (NIFI-2332) When clustered, bulletins not showing the correct node

Mark Payne created NIFI-2332: Summary: When clustered, bulletins not showing the correct node Key: NIFI-2332 URL: https://issues.apache.org/jira/browse/NIFI-2332 Project: Apache NiFi Issue Type:

[jira] [Commented] (NIFI-2268) HandleHttpRequest can use too many tasks and CPU

[ https://issues.apache.org/jira/browse/NIFI-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386425#comment-15386425 ] Mark Payne commented on NIFI-2268: -- I think I would avoid calling context.yield() as that will result in

[jira] [Updated] (NIFI-2332) When clustered, bulletins not showing the correct node

[ https://issues.apache.org/jira/browse/NIFI-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2332: - Assignee: Mark Payne Status: Patch Available (was: Open) > When clustered, bulletins not showing

[jira] [Created] (NIFI-2334) When looking at Cluster page, some nodes do not show any any stats while others do

Mark Payne created NIFI-2334: Summary: When looking at Cluster page, some nodes do not show any any stats while others do Key: NIFI-2334 URL: https://issues.apache.org/jira/browse/NIFI-2334 Project:

[jira] [Created] (NIFI-2337) IllegalMonitorStateException when disconnecting node

Mark Payne created NIFI-2337: Summary: IllegalMonitorStateException when disconnecting node Key: NIFI-2337 URL: https://issues.apache.org/jira/browse/NIFI-2337 Project: Apache NiFi Issue Type:

[jira] [Updated] (NIFI-2334) When looking at Cluster page, some nodes do not show any stats while others do

[ https://issues.apache.org/jira/browse/NIFI-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2334: - Status: Patch Available (was: Open) > When looking at Cluster page, some nodes do not show any stats

[jira] [Closed] (NIFI-2336) When the current process group is started or stopped, the flow is not saved

[ https://issues.apache.org/jira/browse/NIFI-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne closed NIFI-2336. > When the current process group is started or stopped, the flow is not saved >

[jira] [Updated] (NIFI-2292) Nodes in cluster sometimes become out-of-sync with actual 'connection state' of node

[ https://issues.apache.org/jira/browse/NIFI-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2292: - Description: Occasionally I'll see a node that has a different view of the cluster than other nodes.

[jira] [Created] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster

Mark Payne created NIFI-2305: Summary: Nodes run "Primary Node Only" processors when disconnected from cluster Key: NIFI-2305 URL: https://issues.apache.org/jira/browse/NIFI-2305 Project: Apache NiFi

[jira] [Updated] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster

[ https://issues.apache.org/jira/browse/NIFI-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2305: - Fix Version/s: 0.8.0 > Nodes run "Primary Node Only" processors when disconnected from cluster >

[jira] [Updated] (NIFI-1992) Update Site-to-Site Client to support Zero-Master Clustering Paradigm

[ https://issues.apache.org/jira/browse/NIFI-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-1992: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update Site-to-Site Client to support

[jira] [Updated] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'

[ https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2289: - Status: Patch Available (was: Open) > Cluster sometimes gets into state where it always says 'no Cluster

[jira] [Created] (NIFI-2290) List Queue not working properly in clustered mode

Mark Payne created NIFI-2290: Summary: List Queue not working properly in clustered mode Key: NIFI-2290 URL: https://issues.apache.org/jira/browse/NIFI-2290 Project: Apache NiFi Issue Type: Bug

[jira] [Created] (NIFI-2316) After restarting cluster, all nodes sometimes come up with all components stopped

Mark Payne created NIFI-2316: Summary: After restarting cluster, all nodes sometimes come up with all components stopped Key: NIFI-2316 URL: https://issues.apache.org/jira/browse/NIFI-2316 Project:

[jira] [Created] (NIFI-2318) Node Events shown in cluster table often indicate that the node's status changed to CONNECTED many times

Mark Payne created NIFI-2318: Summary: Node Events shown in cluster table often indicate that the node's status changed to CONNECTED many times Key: NIFI-2318 URL: https://issues.apache.org/jira/browse/NIFI-2318

[jira] [Created] (NIFI-2324) If we reach the maximum number of outstanding HTTP requests, logs should indicate which requests are outstanding

Mark Payne created NIFI-2324: Summary: If we reach the maximum number of outstanding HTTP requests, logs should indicate which requests are outstanding Key: NIFI-2324 URL:

[jira] [Updated] (NIFI-2017) Root Group Port Transmission Icon is inaccurate

[ https://issues.apache.org/jira/browse/NIFI-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2017: - Fix Version/s: (was: 1.0.0) 1.1.0 > Root Group Port Transmission Icon is inaccurate

[jira] [Commented] (NIFI-2017) Root Group Port Transmission Icon is inaccurate

[ https://issues.apache.org/jira/browse/NIFI-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384707#comment-15384707 ] Mark Payne commented on NIFI-2017: -- [~mcgilman] - I believe you are correct, in that this is a

[jira] [Updated] (NIFI-2316) After restarting cluster, all nodes sometimes come up with all components stopped

[ https://issues.apache.org/jira/browse/NIFI-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2316: - Status: Patch Available (was: Open) > After restarting cluster, all nodes sometimes come up with all

  1   2   3   4   5   6   7   8   9   10   >