Run out of slots in the query output buffer

Follow

Gianfranco Campana

• December 21, 2022 10:06
• Edited

I'm having the message

Waring
Could not render chart

Run out of slots  in the query output buffer

 

just randomly in some chart in my dashboard.
One time on a chart, another time in another.
There is no way to fix the chart ( the chart is shown empty with the message), the only thing I can do is delete and recreate the same chart, from that time it works properly again.

What exactly this message means and  how can I avoid it?

I'm running heavyai 6.2.7 on Ubuntu docker free GPU GTX1080 8GB, 128 GB Ram.
The dashboard reads  a little table with 65k rows and has two pages with a number of different charts on that table.
The chart that lead to the error last time, is a simple chart with 25 Dimensions and 0 measures.

 

 

0

• 

  Gianfranco Campana

  • January 02, 2023 08:52
  • Edited

  Just happened again ^_^

  I lost my dashboard - there is no way to re-enter and edit the dashboard that doesn't open because this error.

  After this, i proceeded to upgrade to version  6.4.0, and the dashboard worked again.
  This makes me think that next time I could delete and re-pull the container as a workaround (???).

  Anyway some other details on this issue:in the dashboard there are several charts built on a 160K rows and about 30 columns table, and a view with 1000 rows 2 columns created on the same table.

  The query the failed this time with "Run out of slots  in the query output buffer"  is the query that create the view:

  SELECT
        dataora,
        PG_DATE_TRUNC('DAY', dataora) AS giorno,
        COUNT(utente) AS c
      FROM
        operint
      GROUP BY
        dataora,
        PG_DATE_TRUNC('DAY', dataora)

   

  0

  Comment actions Permalink
• 

  Candido Dessanti

  • January 02, 2023 08:25

  Hi Gianfranco Campana,

   

  Thanks for joining the new community; I'm sorry for this late reply. I missed the notification about those messages.

  To mitigate this error, you can try setting the parameter use-estimator-result-cache to false.

  Can you get the queries that are causing this error? When using immerse, you can get the queries by activating the SQL logging feature in the browser following this procedure.

  • Open the developer tools (typically using the f12 key on the browser), go into the console, and type window.SQLlogging(true).
  • After that, reload the page (typically F5) to enable the property.

  You should see the fired queries directly in the console.
  Or you can send us directly the logs of the product taking them from the filesystem or getting the last one from immerse following this URL https://[your_instance]:6273/logs/info
  
  Let me know if you are still having the issue.
  
  Regards,
  Candido

   

  0

  Comment actions Permalink
• 

  Gianfranco Campana

  • January 02, 2023 08:57

  Thank you Candido,

  I already intercepted the query and reproduced the error outside Immerse, it's the query I reported in the last message. Thanks anyway for the hints, I' ll give a try to use-estimator-result-cache parameter.

   

  0

  Comment actions Permalink

Please sign in to leave a comment.