RAT check failure

I attempted to run 'mvn -Pcontrib-chewck clean install' prior to submitting a PR. It fails with the following RAT checks. (Note: this occurs on master as well, so it is nothing introduced by my changes.) [INFO] Enabled default license matchers. [INFO] Will parse SCM ignores for exclusions... [INFO

Re: RAT check failure

n any phase of the maven > build. You have probably built nifi-grpc-bundle in the past in your > workspace. > > -- Mike > > > On Sat, Mar 10, 2018 at 12:13 PM, Mark Bean wrote: > > > I attempted to run 'mvn -Pcontrib-chewck clean install' prior to > s

penalized MockFlowFile

The MockFlowFile has a method setPenalized() which sets the 'penalized' variable to true. And, the isPenalized() method simply returns the value of 'penalized'. (In the real world, isPenalized() is time-based.) How does one un-penalize a MockFlowFile? I believe an unsetPenalized() method may be nee

status bar counts on a cluster

On a cluster, the status bar reports 4 invalid processors. However, on some nodes there are actually 6 invalid processors. The extra two processors are invalid because a required configuration file (a property of the processor) does not exist on some nodes. The count on the status bar is not comin

Search for Controller Service UUID

When I search for a Controller Service by UUID using the search on the toolbar, only processors which reference the service are listed, not the service itself. Similarly, when selecting the UUID from the Bulletin Board, it reports "Error: Unable to find the specified component". Is this by design?

Re: status bar counts on a cluster

This seems to have slipped through the cracks; I haven't seen a response. Does anyone have input? Thanks, Mark On Fri, Apr 20, 2018 at 10:40 AM, Mark Bean wrote: > On a cluster, the status bar reports 4 invalid processors. However, on > some nodes there are actually 6 invalid proc

Cluster behavior when heavily loaded

We have a 6-node cluster using external ZooKeeper. It is heavily loaded, and we are attempting to tune some of the properties to alleviate some observed issues. By "heavily loaded" I mean the graph is large (approx. 3,000 processors) and there is a lot of data in process (approx. 2M flowfiles/120GB

PR AppVeyor build failure

It appears the AppVeyor build failed on my PR [1]. It also appears that it simply timed out after 90 minutes. Is there a way to re-run this check? [1] https://github.com/apache/nifi/pull/2703 Thanks, Mark

Re: [DISCUSS] Release candidate timeframe for Apache NiFi 1.7.0

I updated NIFI-4907 to have a fix version of 1.7.0. -Mark On Tue, Jun 5, 2018 at 3:09 PM, Andy LoPresto wrote: > Sending out an update. I am using the following search query to take a > look at what is still outstanding for 1.7.0. Currently I have visibility on > the following issues: > > proj

API endpoint for /resources

What information specifically does the Rest API endpoint "/resources" provide? Also, a user belongs to every policy, and when hitting that endpoint still receives "No applicable policies could be found. Contact the system administrator." Is the "/resources" endpoint still supported? Thanks, Mark

Re: API endpoint for /resources

policies for. > > As far as I know, a user would need READ to /resources to make a > request to the end-point. > > Thanks, > > Bryan > > > On Thu, Jun 7, 2018 at 8:13 AM, Mark Bean wrote: > > What information specifically does the Rest API endpoint "/resour

Re: [DISCUSS] Change of Cluster Flow Inheritance

Great ideas Mark. Another addition for ease/convenience of a node joining a cluster is related to the authorizations.xml and users.xml. In the case of the flow.xml.gz, if the file is missing, it will obtain a copy from the cluster. The same should be true of authorizations.xml and users.xml files,

Upgrading NiFi Registry

How does one upgrade the NiFi Registry? After unpacking the .tar.gz file, how does one get all the flows registered in a previous version of NiFi Registry into the newly installed version? And, how does one ensure all the policies transfer as well? Thanks, Mark

Re: Upgrading NiFi Registry

e same as NiFi... stored in users.xml and > authorizations.xml the conf directory, depending how you configured > everything. So just copying those two files over to the new install. > > -Bryan > > > On Wed, Jun 20, 2018 at 11:13 AM, Mark Bean wrote: > > How does one upgrade the NiFi

validation changes in 1.7.0

Several of our custom processors are not compatible with version 1.7.0. There is a growing pattern of unit test failures due to customValidate() not being executed now where it was being executed in 1.6.0 and prior. I believe there were changes made in 1.7.0 in terms of how validation - and therefo

Re: validation changes in 1.7.0

ctive of the Test Runner) to validate a > > > > component that got removed in some of this refactoring. > > > > > > > > I do see in StandardProcessorTestRunner (the impl of the TestRunner > > > interface) that when run() is called, are still > > >

Re: validation changes in 1.7.0

e Processor > and all referenced services are valid. > > Thanks > -Mark > > > [1] https://issues.apache.org/jira/browse/NIFI-5368 > > > On Jul 3, 2018, at 8:55 AM, Mark Bean mark.o.b...@gmail.com>> wrote: > > This issue is not related to EL. I've tr

Re: validation changes in 1.7.0

until 1.8.0 or hopefully a quick turn-around on 1.7.1 - or even minimally the completion of NIFI-5368 that we could apply to a forked version. Thanks, Mark B. On Tue, Jul 3, 2018 at 10:15 AM Mark Bean wrote: > Mark, > > You're exactly correctly. I discovered the w

Re: [discuss] should we do a nifi 1.7.1 release?

+1 for a 1.7.1 release if it contains a fix for NIFI-5368 [1]. This bug is breaking multiple unit tests on custom processors. [1] https://issues.apache.org/jira/browse/NIFI-5368 On Thu, Jul 5, 2018 at 12:23 PM Joe Witt wrote: > team, > > Wanted to kick off a thread to suggest we do a nifi 1.7

Re: [discuss] should we do a nifi 1.7.1 release?

prashant...@nokia.com> wrote: > > Thanks Andy.. +1 for 1.7.1 release. > > Thanks & Regards, > Prashanth > > From: Andy LoPresto [mailto:alopre...@apache.org ] > Sent: Friday, July 06, 2018 1:34 AM > To: dev@nifi.apache.org > Subject: Re: [discuss] should we do a n

[DISCUSS] NiFi shared file system

I'd like to start a discussion on making NiFi Clustering more robust. As it is, a Cluster is very beneficial from a management standpoint. A change only needs to be made in one place - any place - and it is replicated across the cluster. However, from a data perspective, the same flexibility is not

Re: [VOTE] Release Apache NiFi 1.7.1

+1 (non-binding) Signature and hashes look good Commit matches Build with contrib-check passes Installed binary and ran trivial flows to verify installation On Sat, Jul 14, 2018 at 3:53 PM Aldrin Piri wrote: > +1, binding > > hashes and signature looked good > full build with contrib-check pass

Controllser Service validation

Scenario: We have a custom Controller Service which was deprecated in favor of its replacement (also custom.) The original CS extends the new CS, and contains just a single method: customValidate. This remained intact to log a message saying "Don't use me.. use the new one." When NiFi was re-start

Oracle ODBCConnectionPool driver

What driver is required to connect to an Oracle database using the DBCPConnectionPool Controller Service? Will the same driver work for both 11g and 12c databases? Thanks, Mark

Re: Oracle ODBCConnectionPool driver

etty good on backward compatibility as far as I know. > >> On Tue, Oct 16, 2018 at 11:06 PM Mark Bean wrote: >> >> What driver is required to connect to an Oracle database using the >> DBCPConnectionPool Controller Service? Will the same driver work for both >> 11g and 12c databases? >> >> Thanks, >> Mark >>

Load Balancing

I am trying to understand how the load balancing works in NiFi 1.8.0. I have a 2-node Cluster. I set an UpdateAttribute to set the value of a property, "balancer", to either 0 or 1. I am using stateful EL for this: ${getStateValue('balancer'):plus(1):mod(2)}. The connection for the output of the

zero downtime upgrade to 1.8.0

I attempted to upgrade a 3-node Cluster from 1.6.0 to 1.8.0. The process I used was to configure 1.8.0 on all Nodes. Then, one Node at a time, shutdown the 1.6.0 and startup the 1.8.0 version. For the first Node, I copied the flow.xml.gz from the previous 1.6.0 installation. (The authorizations.xml

Re: zero downtime upgrade to 1.8.0

ou'd need to give yourself in > that case. Have you already looked there? > > And finally, hard refresh to clear cache is also a possible path > > Thanks > On Fri, Nov 2, 2018 at 12:26 PM Mark Bean wrote: > > > > I attempted to upgrade a 3-node Cluster from 1.6

Re: [DISCUSS] Extension Registry

I would like to see a "group" capability in the Registry for NAR bundles. Then, users can create their own customized grouping of relevant NARs. Managing bundles one at a time will become tedious. Thanks, Mark On Tue, Nov 13, 2018 at 12:48 PM Joe Witt wrote: > Sivaprasanna - yes absolutely. Th

Re: [DISCUSS] Extension Registry

flows are designed > against specific components that come from certain nars for which we > know the precise coordinates. When importing flows that depend on > these the system will be able to automatically acquire all that it > needs. > > Thanks > On Tue, Nov 13, 2018 at 12:57

Re: [EXT] [discuss] release apache nifi 1.9.0

I have an open PR I'd like included in 1.9. It's a very simple one. https://github.com/apache/nifi/pull/3053 Thanks, Mark On Wed, Feb 6, 2019 at 7:43 PM Joe Witt wrote: > i have that one ready to go andy. ill take care of the dev docs one. > > thanks > > On Wed, Feb 6, 2019, 7:24 PM Andy LoPr

Funnels and available thread count

It seems that funnels should not require a thread; they do not actually process data. However, looking into the code for both 1.8.0 [1] and master [2], it seems that a thread is allocated to each funnel when gathering the status of a Process Group. Does this count against threads available to be al

Re: Funnels and available thread count

til the next target isn't a > funnel. Could do the same with local ports.. > > Thanks > > On Fri, Feb 8, 2019 at 10:23 AM Mark Bean wrote: > > > It seems that funnels should not require a thread; they do not actually > > process data. However, looking into the co

Re: [EXT] [discuss] release apache nifi 1.9.0

> > author; > > > > you > > > > > > >> want > > > > > > >> > those > > > > > > >> > > > > > same > > > > > > >> > > > > > > comments to be addressed. > > > > > > >> > > >

global and component access policies

There is a global level access policy for 'access all policies' (view and modify). These access policies apply to components (e.g. processor) as well as the controller. Even if a user is explicitly excluded from the component level access policy 'view/modify the policies', the user still has access

Re: global and component access policies

the UI since the behavior is > different from how component policies override ancestor policies. This > choice was made since it allowed for folks to define an administrator for > all things and local/component level administrators. > > Matt > > On Fri, Feb 22, 2019 at 3:03 PM Mark

initial component access policies

When NiFi is started for the first time, the Component Access Policies are not populated even for the Initial Admin or for legacy DFM_ROLE users in authorized-users.xml file.That is, not unless a flow.xml.gz file exists. The fact that the admin user does not have access to these policies has led to

Re: initial component access policies

parseFlow() method above which tries to > read the flow.xml.gz from disk, using the location from nifi.properties. > > > > On Apr 2, 2019, at 9:57 PM, Mark Bean wrote: > > > > When NiFi is started for the first time, the Component Access Policies > are > > not

Node Group property usage

What is the proper usage of the Node Group in the authorizers.xml file? The documentation only describes what it is, but not how to use it. For example, I attempt to add a new node to a cluster. The authorizers.xml was modified to add the User Group name to the accessPolicyProvider's Node Group pr

Re: Node Group property usage

ew node, as long as > they are in that group in the user-group-provider. > > On Thu, Apr 11, 2019 at 2:53 PM Mark Bean wrote: > > > > What is the proper usage of the Node Group in the authorizers.xml file? > The > > documentation only describes what it is, but not

Re: Suggestion on NIFI UI enhancement

Regarding #1 (empty all queues in a process group), there is a very similar one at https://issues.apache.org/jira/browse/NIFI-5329 also. Perhaps one of these (NIFI-4308 or NIFI-5329) should be marked as duplicate. On Tue, May 7, 2019 at 6:51 AM Otto Fowler wrote: > I found this issue already h

Re: FlowFile Expiration - Lineage vs Queue Times

On a similar note, we recently had a case where it would be desirable for the flowfile expiration to kick in only after the flowfile size/count back pressure limits have been reached. In other words, once a back pressure (size) limit is reached, it would be desirable to then remove flowfiles - begi

Re: [DISCUSS] NiFi Registry 0.5.0 release

I'd like to see NIFIREG-177 included in the next release. It seems like a fairly simple addition, but I have not had time to dig in; I'm not familiar with modifying the UI. I hope someone knowledge of the UI could knock this out fairly quickly? [1] https://issues.apache.org/jira/browse/NIFIREG-177

reset counter

I have a counter which is updated within a custom processor. The UI allows a given counter to be reset to zero. The UI shows an updated value of "0". However, this does not update the underlying counter object's value. So, the next time the counter is incremented, it is adding to the previous, non-

Re: reset counter

Skip this question. The problem was with how the counter values were being updated, and had nothing to do with the reset. On Wed, Sep 11, 2019 at 1:42 PM Mark Bean wrote: > I have a counter which is updated within a custom processor. The UI allows > a given counter to be reset to zero.

Provenance query does not show results

There have been several times on different NiFi instances where the Provenance Query results are not shown. It appears as if there are no provenance events at all. However, after restarting NiFi, the events correctly appear. This has been observed in 1.8.0 and 1.9.2. There is a JIRA ticket [1] whi

Re: Provenance query does not show results

d then the > user is warned and possibly startup is cancelled. > > Thanks > > On Mon, Sep 16, 2019 at 11:25 AM Mark Bean wrote: > > > There have been several times on different NiFi instances where the > > Provenance Query results are not shown. It appears as if there are no

dependency scope

We are building Apache NiFi on a separate network with an internal Nexus repository. When I attempt to build the rel/nifi-1.9.2 tag, I get compilation errors due to an import failing. Specifically, it is com.google.common.cache.Cache (and CacheBulider) in nifi-nar-bundles/nifi-framework-bundle/nif

Re: [discuss] approaching a NiFi 1.10.0 release

Trivial pull request waiting on review; would be nice to get in 1.10.0. https://github.com/apache/nifi/pull/3810 Thanks. On Tue, Oct 15, 2019 at 10:58 AM Joe Witt wrote: > Thanks team. Progressing RC for 1.10.0 tasks now. > > > > On Thu, Oct 3, 2019 at 12:55 PM Bryan Bende wrote: > > > Done!

high task count

We have a PostHTTP with the failure relationship going to a downstream processor. The downstream processor has a huge task count - over 100 million tasks across the cluster in the 5-minute stats window. Yet, there are only between 4,000-18,000 FlowFiles that are processed in that same time. The ex

Re: Re: Re: [Discuss] Data prioritization - A proposed solution

First, I think this idea is fantastic. The ability to move certain high-priority data through the flow faster than other data is a crucial feature which is currently missing - at least in an efficient implementation. I had one thought on getting away from the globally-coupled queue problem. Perhap

Re: [VOTE] Release Apache NiFi 1.10.0 (RC1)

Verified checksums Unzipped source Verified commit IDs Ran build (mvn clean install -Pcontrib-check,include-grpc) on an empty local repo Unpacked binary Started NiFi with default settings Ran a simple flow +1, non-binding On Tue, Oct 22, 2019 at 12:33 PM Joe Witt wrote: > Hello, > > I am pleas

Minimum zookeeper version

For NiFi 1.10.0, what is the minimum version of zookeeper when using an external zookeeper instance? Thanks, Mark

Re: Minimum zookeeper version

> > On Fri, Nov 22, 2019 at 3:30 PM Mark Bean wrote: > > > For NiFi 1.10.0, what is the minimum version of zookeeper when using an > > external zookeeper instance? > > > > Thanks, > > Mark > > >

Re: Programmatically passing secrets to nifi processor.

Bahlul, You can access parameter contexts via the NiFi REST API. See /parameter-contexts under the Controller in the API documentation. http://nifi.apache.org/docs.html -Mark On Mon, Nov 25, 2019 at 1:12 PM Bahlul Haider wrote: > Friendly Monday morning ping. > > I am looking for a way to pro

Re: Programmatically passing secrets to nifi processor.

Thank you Mark for your quick reply. This is what I was looking for but > > was unable to find it. > > > > I will see if I can create the parameter context using the REST APIs. > > > > Thanks, > > Bahlul > > > > On Mon, Nov 25, 2019 at 10:49 AM Mar

Re: Cloned processor not loading

Phil, Add the fully qualified class name of Jerry to the resources file in your bundle: {nifi-custom-bundle}/{nifi-custom-processors}/src/main/resources/META-INF/services/org.apache.nifi.processors.Processor -Mark On Sun, Dec 15, 2019 at 6:09 PM Phil H wrote: > Hi there, > > I have a working

Dynamic property for controller service

I have a custom controller service with dynamic properties. The dynamic property value is expected to be a controller service. Therefore, the getSupportedDynamicPropertyDescriptor returns a PropertyDescriptor from the Builder with "identifiesControllerService(ControllerService.class)". This is beca

Re: Dynamic property for controller service

support. > > Regards, > Matt > > [1] https://issues.apache.org/jira/browse/NIFI-6852 > [2] https://github.com/apache/nifi/pull/3973/files > > On Thu, Jan 9, 2020 at 5:01 PM Mark Bean wrote: > > > > I have a custom controller service with dynamic properties. The

Re: [discuss] Apache NiFi 1.11.0

There's an open PR [1] for NIFI-6852. Could really use this in 1.11.0. [1] https://github.com/apache/nifi/pull/3973 On Mon, Jan 6, 2020 at 12:06 PM Joe Witt wrote: > Team, > > We've already seen a good stream of nice fixes, improvements, and some > minor features land on NIFi 1.11.0. It is eno

Re: [VOTE] Release Apache NiFi 1.11.0 (rc3)

+1, non-binding checked hashes, built from source, installed and ran simple tests (single instance) Java 8, MacOS 10.15.2 On Sun, Jan 19, 2020 at 3:21 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-1.11.0. > > The source zip,

IntelliJ, language level and jigaw profile

I'm having trouble with IntelliJ setting the proper language level. Has anyone else seen the following behavior? IntelliJ 2019.3.2 (Community Edition) installed from ideaIC-2019.3.2-no-jbr.tar.gz File > Project Structure > Platform Settings > SDKs - Only 1.8 is loaded File > Project Structure >

Re: IntelliJ, language level and jigaw profile

at should get you > back to having your classes compiled with Java 8. > > On Wed, Jan 29, 2020 at 4:23 PM Mark Bean wrote: > > > I'm having trouble with IntelliJ setting the proper language level. Has > > anyone else seen the following behavior? > > > >

Re: IntelliJ, language level and jigaw profile

Found it. Profiles are at the top of the list in the Maven tool window. Thanks for the tip. Unchecking the jigsaw profile did the trick. Thanks, Mark On Thu, Jan 30, 2020 at 8:51 AM Mark Bean wrote: > Jeff, > > Can you please be a little more specific where to find the light/bold

Parameters, Registry and sensitive values

When storing a version controlled process group in the NiFi Registry, the relevant Parameter Context will get stored as well. Similarly, when a different NiFi instance instantiates that process group from the Registry, the instance creates the Parameter Context so it can be used by the process grou

Re: Parameters, Registry and sensitive values

flow and associated parameter context > requires setting of sensitive values. This does however provide for rather > simple configuration of a programmatically pushed flow to an instance and > then all params, sensitive or otherwise set, and the flow run. As well as > easy subsequent updates.

Unable to start NiFi when controller service references other controller services

We are having issues when starting NiFi with a custom controller service which allows dynamic properties. The dynamic properties are themselves additional controller services. Enabling the custom controller service after NiFi is running is fine. But, if the service is enabled on startup, NiFi fails

Re: Re: NiFi 1.24.1 or 1.25.0 release date? - NIFI-12513 bug

I think you may be hitting a bug that was introduced in NiFi 1.25.0. See https://issues.apache.org/jira/browse/NIFI-12785 This issue has been resolved and will be fixed in NiFi 1.26.0. On Thu, Apr 11, 2024 at 1:55 PM Martin Fong wrote: > We have installed 1.25.0 and there is no deprecated mess

Re: [VOTE] Release Apache NiFi 1.26.0 (RC1)

+1 (non-binding) Verified keys and hashes Performed a clean build Java 1.8.0_402 Maven 3.9.3 Ubuntu 22.04.4 Performed upgrade from NiFi 1.25.0 Started correctly. Interacted with NiFi Registry 1.25.0 normally. Performed upgrade of NiFi Registry from 1.25.0 Again, behavior and interaction between N

Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)

+1 (non-binding) Verified signature and hashes. Performed full build starting from an empty local maven repo. Maven: 3.9.6 Java 21.0.2, Eclipse Adoptium Ubuntu 24.04.4 Installed binary and started NiFi with all default settings. Ran simple flow and interacted with the UI, looked at metrics,

Re: [Discuss] NiFi 2.0 milestones, where we are?

There are only a couple issues remaining from NIFIDEVS-12400 . Although, this issue is marked as resolved. I don't want the following unresolved issues to fall through the cracks prior to the final 2.0.0 release: https://issues.apache.org/jira/brow

Re: NiFi - Applicable Policies

The files to remove (or rename for temporary safe keeping) that Matthew is referring to are authorizations.xml and users.xml. You will want to properly configure authorizers.xml with an Initial Admin User. Of course, "properly configure" includes having an authenticated user requiring a client use

site-to-site configuration

I am attempting to setup secure site-to-site using NiFi 1.1.1. I have secured NiFi, and am able to access the UI securely via HTTPS. I have set the following security-related properties: nifi.sensitive.props.key= nifi.sensitive.props.key.protected= nifi.sensitive.props.algorithm=PBEWITHMD5AND256BI

Re: site-to-site configuration

te-to-site" with user of the server added. > > Thanks, > > Bryan > > On Thu, Feb 23, 2017 at 12:34 PM, Mark Bean wrote: > > I am attempting to setup secure site-to-site using NiFi 1.1.1. I have > > secured NiFi, and am able to access th

Re: site-to-site configuration

rst then you can add users. > > Thanks, > > Bryan > > On Thu, Feb 23, 2017 at 1:01 PM, Mark Bean wrote: > > Bryan, > > > > The server is listed on the global policy for "retrieve site-to-site > > details". However, I am not able to add users to the &

Access policies

I am attempting to apply Access Policies appropriately. As a very first step, I want to grant a user access to the UI. From the global menu, I chose Users and added the user. Then, again from the global menu, I chose Policies. I added the user to "view the user interface" and "access the controller

Re: Access policies

Without these permissions, the user can still see the data > flow but they will not be able to see details of those components. > > Matt > > On Fri, Feb 24, 2017 at 12:32 PM, Mark Bean wrote: > > > I am attempting to apply Access Policies appropriately. As a very first > &

Re: Access policies

> no space entered in NiFi. > > Thanks, > > Bryan > > On Fri, Feb 24, 2017 at 12:58 PM, Mark Bean wrote: > > Your description is exactly how I would expect things to work. However, > the > > user is not able to access the graph. > > > > The nifi-user

Zookeeper issues at initial Cluster startup

I am attempting to setup a new Cluster with 3 Nodes initially. Each node is reporting zookeeper/curator errors, and the Cluster is not able to connect the Nodes. The error is reported many times per second and is continuous on all Nodes: 2017-02-28 14:22:53,515 ERROR [Curator-Framework-0] o.a.c.f.

Re: Zookeeper issues at initial Cluster startup

in your cluster, regardless of embedded or external ZK) > > state-management.xml, under cluster-provider element: > (set to the connect string to > access your ZK quorum, used by processors to store cluster-based state) > > [1] > https://nifi.apache.org/docs/nifi-docs/html/ad

Re: Zookeeper issues at initial Cluster startup

the second is for leader election. The leader > > election port is only necessary if electionAlg is 1, 2, or 3 > > (default). If electionAlg is 0, then the second port is not necessary. > > If you want to test multiple servers on a single machine, then > > differen

Controller Services tab

Can someone please clarify the difference between the Global Menu -> Controller Settings -> Controller Services tab and Root Canvas -> Configuration button from palette -> Controller Services tab? I would expect that a Controller Service added via the Global Menu would be available at all levels o

Re: Controller Services tab

s used by processors are created from context > > > palette and are based on the process group you are in at the given > > > time (the root canvas is the root process group). This is done for > > > security purposes so that access to the controller services c

Primary Node and Isolated Processors

Can the Primary Node be manually selected by a user? I believe this capability was available in 0.x, but I'm not sure it exists in 1.x. Also, when a processor is configured to run only on the Primary Node, how are the processor's output flowfiles distributed (i.e. load balanced) across the cluster

List/Empty queue on a Cluster

In order to successfully 'List queue', a user must be part of the 'view the data' access policy. Similarly, in order to successfully 'Empty queue', a user must be part of the 'modify the data'. However, in a Cluster configuration, it appears the Cluster Coordinator must also be in the relevant poli

Re: List/Empty queue on a Cluster

nodes in your cluster are added to the policy > and not just the cluster coordinator. > > -- > Arpit > > On Mar 20, 2017, at 12:05 PM, Mark Bean mark.o.b...@gmail.com>> wrote: > > In order to successfully 'List queue', a user must be part of the '

Re: List/Empty queue on a Cluster

node that was the cluster > coordinator? > > If so maybe all of your list/clear operations succeeded with only that > node in the policies, but if you went to the UI from another node > maybe it wouldn't work? > > -Bryan > > On Mon, Mar 20, 2017 at 3:53 PM, Mark Bean

Policy and UI

We just setup a new cluster. A user has been granted: Global policy to access all policies (read and write) Global policy to access the controller (read) Global policy to view system diagnostics (read) Global policy to view the user interface (read) Admin policy for process group NiFi Flow (read)

UI display problem with policies

On the Global Menu, the item Counters is grayed out because the user is not on the 'access counters' policy To to: Global Menu > Policies > access counters/modify Create a new policy (one did not exist yet) Add the user At this point, the Access Policies page correctly shows the user has been added

Re: UI display problem with policies

odify' -Mark On Fri, Apr 7, 2017 at 9:54 AM, Matt Gilman wrote: > Mark, > > Can you check what browser and version you're using? Also, can you open up > the developer tools and see if there are any client side errors? > > Thanks > > Matt > > On Fri, Apr 7, 2

Shutdown of one Node in Cluster

I have a 3-node Cluster with each Node hosting the embedded zookeeper. When one Node is shutdown (and the Node is not the Cluster Coordinator), the Cluster becomes unavailable. The UI indicates "Action cannot be performed because there is currently no Cluster Coordinator elected. The request should

Re: Shutdown of one Node in Cluster

would not want to do this. But when testing, this should be acceptable, yes? On Tue, Apr 11, 2017 at 1:56 PM, Mark Payne wrote: > Mark, > > Are all of your nodes running an embedded ZooKeeper, or only 1 or 2 of > them? > > Thanks > -Mark > > > On Apr 11, 2017, at 1:1

Re: Shutdown of one Node in Cluster

d, so if > your cluster starts getting busy, you'll see far more stable performance > from a standalone > ZooKeeper. > > > > On Apr 11, 2017, at 2:06 PM, Mark Bean wrote: > > > > All 3 nodes are running embedded ZooKeeper. And, the Admin Guide states > &

Re: Shutdown of one Node in Cluster

listed. > > Thanks > -Mark > > > On Apr 11, 2017, at 2:37 PM, Mark Bean wrote: > > > > Ok, will keep the standalone ZooKeeper in mind. > > > > Back to the original issue, any idea why ZooKeeper went to a PENDING > state > > making the cluster unavai

nifi.templats.directory

In NiFi 1.x (as compared to 0.x), any templates are now stored directly in the flow.xml.gz file. Is that correct? If so, what is the purpose (if any) of the nifi.properties entry for "nifi.templates.directory"? Should this property be deprecated/removed?

Documentation for 1.x

I have been asking many questions lately regarding NiFi 1.x because we are in the process of more deliberately evaluating 1.x as it relates to our current production level flows. In the process, I have found the documentation to be incomplete, sometimes incorrect (e.g. typo), contain references to

Re: nifi.templats.directory

templates from 0.x to 1.x. > Otherwise, we would have lost all templates when migrating. > > Thanks > -Mark > > > > On Apr 12, 2017, at 11:40 AM, Mark Bean wrote: > > > > In NiFi 1.x (as compared to 0.x), any templates are now stored directly > in > > t

Re: Documentation for 1.x

ccepting of > improvements and fixes. That being said, there is more documentation on how > to contribute code than there is documentation, and it can depend if it is > in confluence, the processors, or on the web page. Do you have more > specifics? > > Tony > > On Wed, Apr 12,

Re: nifi.templats.directory

hen migrating. > > Thanks > -Mark > > > > On Apr 12, 2017, at 11:40 AM, Mark Bean wrote: > > > > In NiFi 1.x (as compared to 0.x), any templates are now stored directly > in > > the flow.xml.gz file. Is that correct? > > > > If so, what is the p

Cluster using Site-to-Site

In 0.x, one would point a Remote Process Group (RPG) at the NCM. The NCM would then take care of load balancing to the corresponding Input Port on the Nodes. In 1.x, the same behavior is true so long as the RPG points to the Cluster Coordinator. (I believe this is true at least.) Here's the rub. S

  1   2   3   >