This message was deleted.
# troubleshootings
Slackbot
02/03/2023, 7:29 AMThis message was deleted.
v
Vijay Narayanan
02/03/2023, 8:14 AMplease look at the coordinator log and get the complete error. The look was not correctly specified. Also please paste your lookup definition and the sample csv here
d
D K
02/03/2023, 9:03 AMThanks @Vijay Narayanan. Actually total size of our lookup is around 876 MB. So just wanted to check whether it is becauze size of lookup is more and only 10% of heap is what is reserved for lookup?
v
Vijay Narayanan
02/03/2023, 11:04 AMthe size of the lookup should not cause this(I am assuming you have made it offheap). Try with smaller lookup on similar data to check your config first
d
D K
02/03/2023, 11:24 AMWe are able to resolve the error by making following changes to Historicals and Broker
D K
02/03/2023, 11:24 AMon Historicals => druid.lookup.namespace.cache.type=onHeap
D K
02/03/2023, 11:24 AMon Broker druid.lookup.namespace.cache.type=offHeap
D K
02/03/2023, 11:25 AMon Historicals, Heap is 8GB and on Broker Heap is 2 GB
D K
02/03/2023, 11:25 AMnot sure whether this is the right thing to do
v
Vijay Narayanan
02/03/2023, 11:25 AMwith 896 MB you can have the lookup on heap.
d
D K
02/03/2023, 11:27 AMok. Can this be that 10% of heap is required for lookup and in Broker, we have 2GB only and hence 10% of 2GB is lesser than 800MB?
D K
02/03/2023, 12:11 PMalso @Vijay Narayanan one more thing we noted is that heap memory used is increasing now. Is it because cache is set to onHeap?
D K
02/03/2023, 12:12 PMpelase find above the heap used
D K
02/03/2023, 12:13 PMthe number of processing thread is set to 15 ( 16 core machine)
D K
02/03/2023, 12:13 PMSo can this be that each processing thread is creating a copy of lookup?
v
Vijay Narayanan
02/03/2023, 12:16 PMlookup is loaded once in each of historical, broker and the tasks. Processing threads don’t load lookup
d
D K
02/03/2023, 12:17 PMany idea what would have caused the heap usage to 6 GB?
v
Vijay Narayanan
02/03/2023, 12:18 PMdepends on what is going on in the server. Heap is used for calculations and for caching
d
D K
02/03/2023, 12:20 PMok
D K
02/03/2023, 12:20 PMi also get this error
D K
02/03/2023, 12:20 PMError: Resource limit exceeded
Subquery generated results beyond maximum[10000000]
org.apache.druid.query.ResourceLimitExceededException
D K
02/03/2023, 12:20 PMCan setting "injective" to true in lookup cuase this?
v
Vijay Narayanan
02/03/2023, 12:59 PMthis has nothing to with lookup…if you have sub queries in your query then this is the default limit
👍 1
g
Giwrgos Gkοlfopoulos
02/16/2023, 10:11 AMHello.
you said "Actually total size of our lookup is around 876 MB" , how you calculate this?
We are trying to calculate our lookups size and we not find a way.