Ok, will do
Cheers
Conrad
On 06/05/2016, 13:18, "Joe Witt" wrote:
>Conrad,
>
>Glad the upgrade is back on track.
>
>As for the kite/avro and locale case probably best to start another
>thread as it will have a better chance of catching the eye of folks
>with expertise there.
>
>Thanks
>Joe
>
Conrad,
Glad the upgrade is back on track.
As for the kite/avro and locale case probably best to start another
thread as it will have a better chance of catching the eye of folks
with expertise there.
Thanks
Joe
On Fri, May 6, 2016 at 8:05 AM, Conrad Crampton
wrote:
> Hi Joe,
> Thanks for your
Hi Joe,
Thanks for your quick response (again).
You prompted me to look at every node in the cluster with ps aux | grep nifi
and found that two of my nodes were still running 0.5.1. I do remember now that
I was experiencing an odd thing with these in that everytime I did a service
nifi stop, I w
Conrad,
Inside the conf/nifi.properties file there is a property called
nifi.version=
You will need to change that to the version you've upgrade to if you
just carried forward the old config file. That value is what ends up
being displayed in the web-ui.
Now, having said this if you are runn
Hi,
I have followed the advice on upgrade planning [1] and [2] and had success
since upgrading from 0.4.1 to 0.6.1 (via .5x) or so I thought!
I am using ansible to perform the upgrades to 6 node cluster but then go into
each server to do a ./nifi.sh install to install new version as service.
Run
