From 1feafc555e4d873345d2c7895625290fe880dcc6 Mon Sep 17 00:00:00 2001 From: Razvan-Daniel Mihai <84674+razvan@users.noreply.github.com> Date: Wed, 11 Nov 2026 12:42:32 +0100 Subject: [PATCH] docs: Describe how to flush Druid segments immediately --- .../demos/pages/nifi-kafka-druid-earthquake-data.adoc | 10 ++++++++++ .../demos/pages/nifi-kafka-druid-water-level-data.adoc | 10 ++++++++++ 2 files changed, 20 insertions(+) diff --git a/docs/modules/demos/pages/nifi-kafka-druid-earthquake-data.adoc b/docs/modules/demos/pages/nifi-kafka-druid-earthquake-data.adoc index 055f4ffd..e199b0e8 100644 --- a/docs/modules/demos/pages/nifi-kafka-druid-earthquake-data.adoc +++ b/docs/modules/demos/pages/nifi-kafka-druid-earthquake-data.adoc @@ -379,6 +379,16 @@ Druid saved roughly 201.5 MiB of data across 73 prefixes. If nothing is listed, Druid has not flushed its data from memory to the deep storage yet. After waiting for roughly an hour, the data should show up. +If you don't want to wait, you can make Druid publish the data to the deep storage right away: + +. Open the Druid web interface (the endpoint `router-https` from your `stackablectl stacklet list` command output). +. Click on `Supervisors` at the top. +. Open the actions menu of the `earthquakes` supervisor and click on `Suspend`. + The running ingestion task stops reading from Kafka, publishes its segments to S3 and finishes. +. Run the `rclone lsf` command from above again. + The prefixes should show up after a short while. +. Open the actions menu of the supervisor again and click on `Resume` to continue the ingestion. + Opening up a prefix for a specific year shows the file containing the data of that year: [source,console] diff --git a/docs/modules/demos/pages/nifi-kafka-druid-water-level-data.adoc b/docs/modules/demos/pages/nifi-kafka-druid-water-level-data.adoc index fa8217fa..84ef8d56 100644 --- a/docs/modules/demos/pages/nifi-kafka-druid-water-level-data.adoc +++ b/docs/modules/demos/pages/nifi-kafka-druid-water-level-data.adoc @@ -587,6 +587,16 @@ One prefix corresponds to one segment, which contains all the measurements of a If nothing is listed, Druid still needs to save its data from memory to the deep storage. After waiting for roughly an hour, the data should show up. +If you don't want to wait, you can make Druid publish the data to the deep storage right away: + +. Open the Druid web interface (the endpoint `router-https` from your `stackablectl stacklet list` command output). +. Click on `Supervisors` at the top. +. Open the actions menu of the `measurements` supervisor and click on `Suspend`. + The running ingestion task stops reading from Kafka, publishes its segments to S3 and finishes. +. Run the `rclone lsf` command for `measurements` from above again. + The prefixes should show up after a short while. +. Open the actions menu of the supervisor again and click on `Resume` to continue the ingestion. + Opening up a prefix for a specific day shows the file containing that day's data: [source,console]