File tree 1 file changed +6
-3
lines changed
1 file changed +6
-3
lines changed Original file line number Diff line number Diff line change @@ -6,19 +6,22 @@ The most common reason for this is that your events are outside the configured w
6
6
minutes, which means that any events with a timestamp older than ten minutes in the past will be dropped. Some things
7
7
to check are:
8
8
9
- 1 . Make sure you are sending events within the windowPeriod. See the [ design document ] ( design.md ) for more information
10
- about how this works.
9
+ 1 . Make sure you are sending events within the windowPeriod. See the
10
+ [ overview ] ( overview.md#segment-granularity-and-window-period ) for more information about how this works.
11
11
2 . Make sure you have set up an appropriate Timestamper and TimestampSpec, so Tranquility and Druid both know
12
12
what timestamp your events have.
13
13
14
14
## My tasks are never exiting.
15
15
16
16
The most common reason for this is that handoff is not occurring- your historical nodes are not loading the segments
17
- created by your realtime tasks (see the [ design document ] ( design .md) for more information about how this works).
17
+ created by your realtime tasks (see the [ overview ] ( overview .md) for more information about how this works).
18
18
19
19
Ensure that your coordinator and historical nodes are running, and that your historical nodes have sufficient capacity
20
20
to load new segments. You'll see warnings or errors in the coordinator logs if they do not.
21
21
22
+ Another possibility is that your windowPeriod is excessively long. Keep in mind that tasks cannot hand off and exit
23
+ until the segmentGranularity interval is over and the windowPeriod has elapsed.
24
+
22
25
## I'm getting strange Jackson or Curator exceptions.
23
26
24
27
Most of Tranquility uses com.fasterxml.jackson 2.4.x, but Curator is still built against the older org.codehaus.jackson.
You can’t perform that action at this time.
0 commit comments