Worked like a charm, thanks!
On Fri, May 19, 2017 at 2:17 PM, ddewaele wrote:
> Sorry, payload should also include the nodeId
>
> curl -v -X PUT -d
> "{\"node\":{\"nodeId\":\"b89e8418-4b7f-4743-bdf4-
> 4a08a92f3892\",\"status\":\"DISCONNECTING\"}}"
> -H "Content-Type: application/json"
> http://
Sorry, payload should also include the nodeId
curl -v -X PUT -d
"{\"node\":{\"nodeId\":\"b89e8418-4b7f-4743-bdf4-4a08a92f3892\",\"status\":\"DISCONNECTING\"}}"
-H "Content-Type: application/json"
http://192.168.122.141:8080/nifi-api/controller/cluster/nodes/b89e8418-4b7f-4743-bdf4-4a08a92f3892
You should be able to put it into DISCONNECTED mode by doing the following
call :
curl -v -X PUT -d "{\"node\":{\"status\":\"DISCONNECTING\”}}” -H
"Content-Type: application/json"
http://192.168.122.141:8080/nifi-api/controller/cluster/nodes/b89e8418-4b7f-4743-bdf4-4a08a92f3892
It should respon
I see. Yeah that sounds like something the jira gilman mentioned will
resolve. Thanks for clarifying. I'm sure that jira will be addressed soon.
On May 19, 2017 1:06 PM, "Neil Derraugh" <
neil.derra...@intellifylearning.com> wrote:
> That's the whole problem from my perspective: it stays CONNE
That's the whole problem from my perspective: it stays CONNECTED. It never
becomes DISCONNECTED. You can't delete it from the API in 1.2.0.
That's why I said it was a single point of failure. The exact semantics of
calling it a single point of failure might be debatable, but the fact that
the c
I believe at the state you describe that down node is now considered
disconnected. The cluster behavior prohibits you from making changes when
it knows not all members of the cluster cannot honor the change. If you
are sure you want to make the changes anyway and move on without that node
you sho
That's fair. But for the sake of total clarity on my own part, after one
of these disaster scenarios with a newly quorum-elected primary things
cannot be driven through the UI and at least through parts the REST API.
I just ran through the following. We have 3 nodes A, B, C with A primary,
and A
Can you provide the contents of the MANIFEST file of your NAR after
deploying your updated NAR?
The MANIFEST file should be at:
nifi_home/work/nar/extensions/-unpacked/META-INF/MANIFEST.MF
On Fri, May 19, 2017 at 3:16 AM, 尹文才 wrote:
> Hi Bryan, I could set a specific version for my customized p
If there is no longer a quorum then we cannot drive things from the UI
but the cluster remaining is in tact from a functioning point of view
other than being able to assign a primary to handle the one-off items.
On Fri, May 19, 2017 at 11:04 AM, Neil Derraugh
wrote:
> Hi Joe,
>
> Maybe I'm missin
Hi Joe,
Maybe I'm missing something, but if the primary node suffers a network
partition or container/vm/machine loss or becomes otherwise unreachable
then the cluster is unusable, at least from the UI.
If that's not so please correct me.
Thanks,
Neil
On Thu, May 18, 2017 at 9:56 PM, Joe Witt
That is correct.
On May 19, 2017 9:47 AM, "ddewaele" wrote:
> We're using docker, and in our failover scenario the machine is rebooted
> and/or the docker system is restarted.
>
> We're currently volume mapping the following :
>
> - /srv/nifi/flow/archive:/opt/nifi/nifi-1.2.0/conf/archive:
We're using docker, and in our failover scenario the machine is rebooted
and/or the docker system is restarted.
We're currently volume mapping the following :
- /srv/nifi/flow/archive:/opt/nifi/nifi-1.2.0/conf/archive:Z
- /srv/nifi/flows:/opt/nifi/nifi-1.2.0/conf/flows:Z
-
/srv/
When a node joins a cluster it writes its node identifier into its local
state. This is in a state directory. Is that directory being removed? If
so it will get a new identifier. Otherwise when the node is started it
will reuse that identifier.
On May 19, 2017 4:13 AM, "ddewaele" wrote:
> We
Sorry Koji,
I have used NiFi in Windows So i can't able to use ExecuteStreamCommand for
it.
It shows error in "System cannot find path Specified"
Is any other way for doing it in windows?
On Fri, May 19, 2017 at 12:50 PM, Koji Kawamura
wrote:
> Hi Prabhu,
>
> I just used MergeContent to confi
Hi Prabhu,
I just used MergeContent to confirm test result. In your case, I
thought the goal is sending queries to SQL Server in order so I think
you don't have to use MergeContent.
Having said that, I came up with an idea. This is kind of a hack but
using ExecuteStreamingCommand to analyze numbe
Hi Koji,
Thanks for your mail.
In your template i have one query regarding if number of files taken by get
file is unknown then MergeContent Processor could not work right? because
you have specify maximum number of bins to be 5.
But in my case i am having dynamic number of file counts.In that c
Hi Prabhu,
I think you can use EnforceOrder processor which is available since
1.2.0, without Wait/Notify processor.
Here is a sample flow I tested how it can be used for use-cases like yours:
https://gist.github.com/ijokarumawak/7e6158460cfcb0b5911acefbb455edf0
Thanks,
Koji
On Fri, May 19, 201
We have a 2 node cluster (centos-a / centos-b). During on of your failover
tests, we noticed that when we rebooted centos-b, sometimes "duplicate" node
entries can be seen in the cluster.
We rebooted centos-b and when it came back online the cluster NiFi saw 2 out
of 3 nodes connected.
centos-b
Hi Bryan, I could set a specific version for my customized processor, but
there's a side effect that the version of NIFI components I referenced in
my processor are also updated to the same version.
I actually referenced DBCPService in my processor and I set the version to
a random version 3.0, and
19 matches
Mail list logo