Chukwa collector and agent don't support the concept of time zone. Hence, it will be difficult to change this. The only place that supports time zone is in the UI javascript code. This design simplifies time zone problem to ensure the software works as intended regardless of time zone policy changes.
If you have strict requirement on the agent side to run on a system with non UTC time zone, then you will want to ensure that the time zone information is sent as part of the log file, and the demux parser handles time zone correctly. Since chukwa collector is dedicated machine, there should be no issue to run the system in UTC time with the hadoop cluster. Hope this helps. Regards, Eric On 3/23/11 11:17 PM, "Ying Tang" <[email protected]> wrote: Hi Eric, But i need to fix the timezone in the chukwa ,because the chukwa will be running in different area . So i wonder if there is a way to fix the time zone in the chukwa source code ? On Thu, Mar 24, 2011 at 12:21 AM, Eric Yang <[email protected]> wrote: Hi, It is recommended to run both Agent and Collector in UTC timezone to avoid day light saving time shift. It is probably less work to set the system timezone to UTC for Chukwa to work properly. The same applies to hadoop cluster clock. Regards, Eric On 3/23/11 1:36 AM, "Ying Tang" <[email protected] <http://[email protected]> > wrote: Do the chukwa agent and collector use the system time zone ? What will happen if the agent node and the collector node use different time zone ? And i want the agent and the collector use the fixed time zone , do i have to modify the code and recompile the source?
