tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/20958-need-to-figure-out-how-to-best-address-this-errorCascade CMS: Discussion 2016-07-06T19:17:24Ztag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-01-13T19:33:42Z2016-01-13T19:33:42Zneed to figure out how to best address this error<div><p>Hi,</p>
<p>This message is a result of the Index Block rendering reaching
the value set for <strong>Maximum Rendered Size of an Index Block
(MB)</strong> 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.</p>
<p>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.</p>
<p>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).</p>
<p>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.</p>
<p>Let me know if this helps and I'll be happy to answer any
followup questions you might have.</p>
<p>Thanks</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-01-15T13:54:08Z2016-01-15T13:54:08Zneed to figure out how to best address this error<div><p>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.</p>
<p>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.</p></div>ediegotag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-01-15T15:25:49Z2016-01-15T15:25:49Zneed to figure out how to best address this error<div><p>I checked the code and it looks like there is some additional
logging that provides this information. When you have a moment, try
this:</p>
<ul>
<li><a href="http://help.hannonhill.com/kb/frequently-asked-questions/how-do-i-enable-debug-logging-for-cascade-server">
Enable DEBUG logging</a> for this class:
<pre>
<code>com.hannonhill.cascade.model.render.task.IBRenderContext</code>
</pre></li>
<li>Load a Page that uses the Index Block in question</li>
<li>Check your log file</li>
</ul>
<p>You should see messages similar to this:<br></p>
<pre>
<code>DEBUG [IBRenderContext] : {User: admin, id: b2b6dfaf0a00016c5e4c03d4437af5de, type: page} Index block {index block name} size so far: {size in bytes}</code>
</pre>
<p>and you can then locate the specific Index Block in
question.</p>
<p>Let me know if this helps!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-01-26T16:42:15Z2016-01-26T16:42:15Zneed to figure out how to best address this error<div><p>Hey there,</p>
<p>Just wanted to check in and see if <a href="http://help.hannonhill.com/discussions/how-do-i/20958-need-to-figure-out-how-to-best-address-this-error#comment_38930617">
my previous comment</a> helped at all. Let me know!</p>
<p>Thanks</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-06-20T18:56:42Z2016-06-20T18:56:42Zneed to figure out how to best address this error<div><p>Does changing the "Maximum Rendered Size of an Index Block (MB)"
in the content preferences require a server restart?</p></div>ediegotag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-06-20T19:16:39Z2016-06-20T19:16:39Zneed to figure out how to best address this error<div><p>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?</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-06-20T19:20:24Z2016-06-20T19:20:24Zneed to figure out how to best address this error<div><p>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.</p></div>ediegotag:help-archives.hannonhill.com,2010-02-09:Comment/389135082016-06-20T19:22:39Z2016-06-20T19:22:39Zneed to figure out how to best address this error<div><p>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.</p></div>Tim