Home → How Do I... →

need to figure out how to best address this error

• Edit

ediego

13 Jan, 2016 07:12 PM

I have created a index block that indexes a "Page" asset for each employee at the university and pulls a lot of their work and profile information. Currently I am getting the error below every time I try to view the index block. I just need a few options on how to best address this.

Error:
An error occurred: Task failed: FinalizeSDRenderTask[]: The index block with path _cascade/blocks/index/all-people renders too much data. Rendering aborted to avoid running out of memory and freezing the system.

You may choose to retry the operation. If the problem persists, please contact a system administrator.

The error has been logged to the system console.

Home

1. Support Staff 1 Posted by Tim on 13 Jan, 2016 07:33 PM

   

   Hi,

   This message is a result of the Index Block rendering reaching the value set for Maximum Rendered Size of an Index Block (MB) in your Content Preferences. It is a safety net to prevent large Index Blocks from consuming the majority of resources on the machine and causing potential performance issues across the system. We leave this at 5MB by default (since 5MB is a pretty large XML document), but it is possible to increase this setting if absolutely needed.

   Our general guideline is that for every 1GB of RAM that you have allocated to the application, you can probably increase that setting by ~3-5MB. So if you have 2GB of RAM allocated to Cascade, you could experiment with setting it closer to 10MB.

   From an implementation standpoint, it's always best to index as little information as possible. So, if there are any options checked in your Index Block that you don't need in order to display the appropriate information, don't include it. If you aren't grabbing data from Pages' Data Definition content, don't include Page XML with the Index Block (this is probably the biggest determining factor in terms of size).

   Another potential option might be to use the Velocity Locator Tool/Query API to get the data that you are indexing with your Index Block.

   Let me know if this helps and I'll be happy to answer any followup questions you might have.

   Thanks

   • Edit

2. 2 Posted by ediego on 15 Jan, 2016 01:54 PM

   

   Is there any way to tell what the current size of the index block is or determine how close it is to hitting the limit defined in the "Maximum Rendered Size of an Index Block (MB)" field.

   I'm trying to determine if there is room for growth for the index or if I should breat the data up into multiple assets.

   • Edit

3. Support Staff 3 Posted by Tim on 15 Jan, 2016 03:25 PM

   

   I checked the code and it looks like there is some additional logging that provides this information. When you have a moment, try this:

   • Enable DEBUG logging for this class:

     com.hannonhill.cascade.model.render.task.IBRenderContext
     

   • Load a Page that uses the Index Block in question
   • Check your log file

   You should see messages similar to this:
   

   DEBUG [IBRenderContext] : {User: admin, id: b2b6dfaf0a00016c5e4c03d4437af5de, type: page} Index block {index block name} size so far: {size in bytes}
   

   and you can then locate the specific Index Block in question.

   Let me know if this helps!

   • Edit

4. Support Staff 4 Posted by Tim on 26 Jan, 2016 04:42 PM

   

   Hey there,

   Just wanted to check in and see if my previous comment helped at all. Let me know!

   Thanks

   • Edit

5. Ryan Griffith closed this discussion on 05 Feb, 2016 04:19 PM.

6. ediego re-opened this discussion on 20 Jun, 2016 06:56 PM

7. 5 Posted by ediego on 20 Jun, 2016 06:56 PM

   

   Does changing the "Maximum Rendered Size of an Index Block (MB)" in the content preferences require a server restart?

   • Edit

8. Support Staff 6 Posted by Tim on 20 Jun, 2016 07:16 PM

   

   It does not. Can you describe the behavior you're seeing? For example, are you increasing that value but still seeing the warnings in your log files about this value being reached?

   • Edit

9. 7 Posted by ediego on 20 Jun, 2016 07:20 PM

   

   yes. I increased the value to 50MB and am still seeing the warning. The block is indexing about 17K page assets and pulling the page data. It may just be a problem of too much data.

   • Edit

10. Support Staff 8 Posted by Tim on 20 Jun, 2016 07:22 PM

    

    Wow, yea that sounds like a lot of content. I don't believe I've ever seen that set to more than 15MB or so in a client instance, so if that message is still appearing when it's set to 50MB, I would probably recommend looking into other possible ways of incorporating that data.

    • Edit

11. Tim closed this discussion on 06 Jul, 2016 07:17 PM.