This message was deleted Apache Druid #general

Join Slack

This message was deleted.

# general

Slackbot

02/14/2023, 3:07 PM

This message was deleted.

Thomas

02/14/2023, 3:10 PM

I’ve tried something like this, but historicals within

report

tier don’t load data

Ian Roberts

02/14/2023, 3:11 PM

This should be possible and that looks correct for the load rules. Can you check the coordinator logs as well as the report tier logs?

Thomas

02/14/2023, 3:17 PM

Actually, I wanted to try to run historicals with

druid.segmentCache.lazyLoadOnStart

enabled

Thomas

02/14/2023, 3:17 PM

I’ve just removed it

Thomas

02/14/2023, 3:17 PM

And in Coordinator logs, I can see this :

Copy code

2023-02-14T15:15:14,911 WARN [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - [report]: insufficient active servers. Cannot balance.

Thomas

02/14/2023, 3:18 PM

I have a single historical in this tier and 1 replica in load rule

Thomas

02/14/2023, 3:26 PM

Copy code

2023-02-14T15:26:12,622 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Balancing segments in tier [_default_tier]
2023-02-14T15:26:12,622 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Found 6 active servers, 0 decommissioning servers
2023-02-14T15:26:12,622 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Processing 700 segments for moving from decommissioning servers
2023-02-14T15:26:12,622 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Processing 1000 segments for balancing between active servers
2023-02-14T15:26:14,715 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - [_default_tier]: Segments Moved: [7] Segments Let Alone: [993]
2023-02-14T15:26:14,715 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Balancing segments in tier [report]
2023-02-14T15:26:14,715 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Found 1 active servers, 0 decommissioning servers
2023-02-14T15:26:14,715 WARN [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - [report]: insufficient active servers. Cannot balance.

Thomas

02/14/2023, 3:27 PM

I’ll add another Historical in that new tier

Thomas

02/14/2023, 3:31 PM

After adding another historical in

report tier

Copy code

2023-02-14T15:31:15,608 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Balancing segments in tier [report]
2023-02-14T15:31:15,608 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Found 2 active servers, 0 decommissioning servers
2023-02-14T15:31:15,608 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - No segments found. Cannot balance.

Ian Roberts

02/14/2023, 3:52 PM

can you see if making it the same as default_tier load rule loads the 3 months?

Ian Roberts

02/14/2023, 3:52 PM

also, try restarting coordinator

Thomas

02/14/2023, 4:49 PM

When I’m using this rule, it works but I loose the capacity to load a different period per tier

Ian Roberts

02/14/2023, 4:52 PM

that verifies everything works though. Try putting the 1 y cold tier back to see if it now works. It should work as others have set up a similar config. What version of druid are you on?

Thomas

02/14/2023, 4:54 PM

I’m running 25.0.0

Thomas

02/14/2023, 5:19 PM

Historicals are pulling and dropping segments, not sure if it goes the right way 😛

Thomas

02/14/2023, 5:25 PM

Yup, they’ve dropped all segments

Ian Roberts

02/14/2023, 5:29 PM

what were your load rules originally, did you have a year then decreased to 3 months?

Thomas

02/14/2023, 5:30 PM

Originally, I had

default_tier

with a P3M + future on this datasource

Thomas

02/14/2023, 5:31 PM

I’m wondering if the load rules order matters here

Thomas

02/14/2023, 5:31 PM

Like I want to load P3M then P1M

Ian Roberts

02/14/2023, 5:31 PM

you may need to mark the segments as used that are past 3 months too?

Thomas

02/14/2023, 5:32 PM

It does not even load the segments in the 1st load rule

Ian Roberts

02/14/2023, 5:32 PM

https://druid.apache.org/docs/latest/operations/rule-configuration.html#reload-dropped-data

Thomas

02/14/2023, 5:36 PM

I forgot to mention that I’m trying to achieve this on a small period before trying on P1Y. I don’t want to edit my original load rule of P3M on default tier. I want to add a new load rule on

report

tier that has a P1M retention period

Thomas

02/14/2023, 5:37 PM

I’ve changed the order of the load rules : P1M first then P3M then drop and it seems to work

Ian Roberts

02/14/2023, 5:38 PM

hmmm ok. I would focus on the log message that says no segments found when you have the report tier added with the longer duration

Thomas

02/14/2023, 6:23 PM

I’ve waited for Druid to finish dropping/loading segments, and it seems that I don’t get what I’ve expected. The P1M segments are located on

report

tier only.

Thomas

02/14/2023, 6:23 PM

I’d like to also have those P1M segments loaded on

default_tier

as well

Open in Slack

Previous Next