Thanks Matt - and sorry for the delayed response
I think this approach would work well for me, so I look forward to trying it
out once it has been released.
-Tim
> On Oct 18, 2019, at 1:49 PM, Matt Burgess wrote:
>
> Tim,
>
> The "secondary flow" issue is something I wanted to address as we
i'm trying to use invokehttp to post a file to a webserver. for
smaller files this seems to work just fine, but i try to send a larger
file, i get snagged with this
2019-10-30 14:47:59,188 ERROR [Timer-Driven Process Thread-10]
o.a.nifi.processors.standard.InvokeHTTP
InvokeHTTP[id=a2046302-016a-1
Yes of course… 4 servers.
From: "Wesley C. Dias de Oliveira"
Reply to: "users@nifi.apache.org"
Date: Wednesday, 30 October 2019 at 16:56
To: "users@nifi.apache.org"
Subject: Re: NiFi WebGUI Timestamp issue
Are you using NTP servers?
Em qua, 30 de out de 2019 às 11:36,
mailto:josef.zahn...@sw
Hi Wyllys, sorry for my late reply. 1.10 release in progress, expected soon.
Regards,
Peter Turcsanyi
On Fri, Oct 4, 2019 at 10:22 PM Wyllys Ingersoll <
wyllys.ingers...@keepertech.com> wrote:
>
> Yes, thanks. Is there an ETA for 1.10?
>
> On Fri, Oct 4, 2019 at 3:05 PM Peter Turcsanyi
> wrote
Are you using NTP servers?
Em qua, 30 de out de 2019 às 11:36, escreveu:
> Hi Wesley
>
>
>
> I didn’t change anything on the machine during the time when I restarted
> the cluster (multiple times), however NiFi showed after each restart
> different timestamps/localizations.
>
>
>
> Cheers Josef
The approach we use for disaster recovery might be a start.
* nifi (user) has a cron job that runs BASH script on PROD server node
which copies the flow.xml.gz file to be used on another cluster to a temp
folder.
* The script decrypts the current passwords/properties in flow.xml.gz
Hi Wesley
I didn’t change anything on the machine during the time when I restarted the
cluster (multiple times), however NiFi showed after each restart different
timestamps/localizations.
Cheers Josef
From: "Wesley C. Dias de Oliveira"
Reply to: "users@nifi.apache.org"
Date: Wednesday, 30 Oc
Hi, Josef.
It seems to be related to machine time settings.
Have you checked this?
Em qua, 30 de out de 2019 às 06:57, escreveu:
> Hi Guys,
>
>
>
> We just faced an issue with the time shown in the NiFi webgui (Screenshot
> below).
>
>
>
> We are in Switzerland, so at the moment we have “CET”
Hi Guys,
We just faced an issue with the time shown in the NiFi webgui (Screenshot
below).
We are in Switzerland, so at the moment we have “CET” (UTC + 1h). After a
restart of our 8-node NiFi 1.9.2 cluster, NiFi suddenly showed “CET” - but the
timestamp was in fact UTC, so minus 1h. Then we de
