About oliver

oliver · ‎05-31-2017

Great find, thanks!

oliver · ‎05-31-2017

I should have added - this is HDF 2.1.2 so NiFi 1.1.0

oliver · ‎05-31-2017

@Matt Clarke thanks, but I am running ntp on all machines, my /etc/localtime all point to the same place (in my case /usr/share/zoneinfo/America/Toronto), and, crucially, the date command on each system returns the same thing, which reports back as EDT, eg: Wed May 31 13:21:29 EDT 2017 I don't think the problem lies with my servers...

oliver · ‎05-31-2017

I'm in the America/New_York timezone and my servers run ntp, and they show the right time. The header of NiFi running on those servers is off by one hour, eg system time says 11:00 and NiFi says 10:00. This question is very similar to https://community.hortonworks.com/questions/76724/change-timezone-in-nifi.html but I've tried that solution and no joy. This feels like a daylight savings problem, as the gui says 10:00:00 EST, and really that should be EDT since at time of writing it is summer. I'm using Oracle Java 1.8.0_71. Any ideas?

oliver · ‎02-24-2017

Thanks for writing this up @Matt Clarke - very helpful. Do you have a rule of thumb for a maximum heap size? Is there a limit where garbage collection will surely cause more problems than any gains from further increases in heap?

Online	Offline
Last Visited	‎03-13-2018 07:38 PM

Member Since	‎02-25-2016 03:02 PM
Last Visited	‎03-13-2018 07:38 PM
Posts	32
Kudos received	16

Cloudera Community

Re: NiFi clock is off by one hour (daylight saving...

Re: NiFi clock is off by one hour (daylight saving...

Re: NiFi clock is off by one hour (daylight saving...

Resolving Apache NiFi Time Offset Issues Caused by...

Re: How to address JVM OutOfMemory errors in NiFi.