- 09 8月, 2014 1 次提交
-
-
由 Gian Merlino 提交于
Old: Merged segments are deleted upon successful push, or on IOException. New: Merged segments are deleted on any Exception, but NOT successful push. Deleting a merged segment means that the next merge-and-push run will try to push it again. So we want that to happen if there was any sort of Exception. We *don't* want it to happen if the merge-and-push was successful, since in that case, we are just waiting for historical nodes to load the segment. It might take a while, but there's no reason to re-push while waiting.
-
- 07 8月, 2014 8 次提交
-
-
由 fjy 提交于
separate cleanup of overshadowed vs. unavailable segments
-
由 Xavier Léauté 提交于
-
由 Xavier Léauté 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 fjy 提交于
Coordinator drop/remove related stuff.
-
由 Gian Merlino 提交于
- DruidCoordinatorCleanup should wait for availableSegments to populate before dropping any segments. - Clarify that millisToWaitBeforeDeleting applies to "removing" rather than "dropping" segments. - LoadRule shouldn't need to wait for the deletionWaitTime before dropping excess replicas.
-
- 06 8月, 2014 7 次提交
- 05 8月, 2014 2 次提交
-
-
由 fjy 提交于
Only emit query metrics for uncached queries.
-
由 Gian Merlino 提交于
-
- 02 8月, 2014 17 次提交
-
-
由 Xavier Léauté 提交于
-
由 Xavier Léauté 提交于
-
由 Xavier Léauté 提交于
-
由 Xavier Léauté 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 Xavier Léauté 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 fjy 提交于
-
由 Xavier Léauté 提交于
-
由 Xavier Léauté 提交于
-
由 fjy 提交于
-
由 fjy 提交于
doc for IngestSegmentFirehose
-
- 01 8月, 2014 5 次提交
-
-
由 nishantmonu51 提交于
-
由 fjy 提交于
-
由 fjy 提交于
Conflicts: docs/content/toc.textile
-
由 fjy 提交于
-
由 fjy 提交于
-