From c9393e52890ff256b4a9493ca63265aa6fc721e1 Mon Sep 17 00:00:00 2001 From: Charles Allen Date: Mon, 1 Feb 2016 08:51:07 -0800 Subject: [PATCH] Add more docs around timezone handling * Fixes #2356 --- docs/content/configuration/index.md | 2 +- docs/content/operations/recommendations.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/configuration/index.md b/docs/content/configuration/index.md index a237d55c6611..7a259870993e 100644 --- a/docs/content/configuration/index.md +++ b/docs/content/configuration/index.md @@ -10,7 +10,7 @@ This describes the common configuration shared by all Druid nodes. These configu There are four JVM parameters that we set on all of our processes: -1. `-Duser.timezone=UTC` This sets the default timezone of the JVM to UTC. We always set this and do not test with other default timezones, so local timezones might work, but they also might uncover weird and interesting bugs. +1. `-Duser.timezone=UTC` This sets the default timezone of the JVM to UTC. We always set this and do not test with other default timezones, so local timezones might work, but they also might uncover weird and interesting bugs. To issue queries in a non-UTC timezone, see [query granularities](../querying/granularities.html#period-granularities) 2. `-Dfile.encoding=UTF-8` This is similar to timezone, we test assuming UTF-8. Local encodings might work, but they also might result in weird and interesting bugs. 3. `-Djava.io.tmpdir=` Various parts of the system that interact with the file system do it via temporary files, and these files can get somewhat large. Many production systems are set up to have small (but fast) `/tmp` directories, which can be problematic with Druid so we recommend pointing the JVM’s tmp directory to something with a little more meat. 4. `-Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager` This allows log4j2 to handle logs for non-log4j2 components (like jetty) which use standard java logging. diff --git a/docs/content/operations/recommendations.md b/docs/content/operations/recommendations.md index 752703b434e3..d938285256ff 100644 --- a/docs/content/operations/recommendations.md +++ b/docs/content/operations/recommendations.md @@ -7,7 +7,7 @@ Recommendations # Use UTC Timezone -We recommend using UTC timezone for all your events and across on your nodes, not just for Druid, but for all data infrastructure. This can greatly mitigate potential query problems with inconsistent timezones. +We recommend using UTC timezone for all your events and across on your nodes, not just for Druid, but for all data infrastructure. This can greatly mitigate potential query problems with inconsistent timezones. To query in a non-UTC timezone see [query granularities](../querying/granularities.html#period-granularities) # SSDs