<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server</link><pubDate>Wed, 19 Mar 2025 18:39:34 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6fd06938-333b-4e24-aecc-89e2140cc8a5</guid><dc:creator>pauline.delacruz</dc:creator><comments>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server#comments</comments><description>Current Revision posted to Appian Knowledge Base by pauline.delacruz on 3/19/2025 6:39:34 PM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When utilizing functionality that requires the search server, the following error message is printed in the application server log:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Caused by: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], all shards failed; shardFailures {[90nFgyfMQPmYsbhzr2aI7w][xray-rule-execution][0]: ElasticsearchException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: UncheckedExecutionException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]; nested: ExecutionError[java.lang.OutOfMemoryError: Java heap space]; nested: OutOfMemoryError[Java heap space]; } 
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The error is seen when one of the search server functionalities requires more JVM heap than the configured maximum limit. By default, the search server will start with the configurations for initial and maximum memory usage (JVM heap) each set to 1024MB (1GB).&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Starting with Appian 17.2, rule performance metrics are aggregated every minute to help save on disk space and heap memory. Please upgrade to this version of Appian to help mitigate the heap issues in your environment.&lt;/p&gt;
&lt;h2&gt;Workaround&lt;/h2&gt;
&lt;p&gt;If upgrading to Appian 17.2 is not feasible, perform the following to manually increase the heap on the search server machine (&lt;strong&gt;Note:&lt;/strong&gt; The machine must be equipped to handle additional memory on the search server machine. Do not attempt these steps on a box that consistently runs high on memory):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Follow the steps mentioned in &lt;a href="https://docs.appian.com/suite/help/latest/Search_Server.html#Starting_and_Stopping"&gt;Starting and Stopping the Search Server&lt;/a&gt; to increase the search server heap limit.&lt;/li&gt;
&lt;li&gt;Stop the application server.&lt;/li&gt;
&lt;li&gt;Stop the search server.&lt;/li&gt;
&lt;li&gt;Recreate the indices before restarting the search server by following the action in&amp;nbsp;&lt;a href="/support/w/kb/3550/kb-1082-issues-related-to-search-server-indices"&gt;KB-1082&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Start the search server.&lt;/li&gt;
&lt;li&gt;Start the application server.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed: March&lt;span&gt;&amp;nbsp;2025&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: administration, heap, search server, infrastructure&lt;/div&gt;
</description></item><item><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server/revision/6</link><pubDate>Mon, 10 Mar 2025 21:39:52 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6fd06938-333b-4e24-aecc-89e2140cc8a5</guid><dc:creator>pauline.delacruz</dc:creator><comments>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server#comments</comments><description>Revision 6 posted to Appian Knowledge Base by pauline.delacruz on 3/10/2025 9:39:52 PM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When utilizing functionality that requires the search server, the following error message is printed in the application server log:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Caused by: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], all shards failed; shardFailures {[90nFgyfMQPmYsbhzr2aI7w][xray-rule-execution][0]: ElasticsearchException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: UncheckedExecutionException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]; nested: ExecutionError[java.lang.OutOfMemoryError: Java heap space]; nested: OutOfMemoryError[Java heap space]; } 
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The error is seen when one of the search server functionalities requires more JVM heap than the configured maximum limit. By default, the search server will start with the configurations for initial and maximum memory usage (JVM heap) each set to 1024MB (1GB).&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Starting with Appian 17.2, rule performance metrics are aggregated every minute to help save on disk space and heap memory. Please upgrade to this version of Appian to help mitigate the heap issues in your environment.&lt;/p&gt;
&lt;h2&gt;Workaround&lt;/h2&gt;
&lt;p&gt;If upgrading to Appian 17.2 is not feasible, perform the following to manually increase the heap on the search server machine (&lt;strong&gt;Note:&lt;/strong&gt; The machine must be equipped to handle additional memory on the search server machine. Do not attempt these steps on a box that consistently runs high on memory):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Follow the steps mentioned in &lt;a href="https://docs.appian.com/suite/help/latest/Search_Server.html#Starting_and_Stopping"&gt;Starting and Stopping the Search Server&lt;/a&gt; to increase the search server heap limit.&lt;/li&gt;
&lt;li&gt;Stop the application server.&lt;/li&gt;
&lt;li&gt;Stop the search server.&lt;/li&gt;
&lt;li&gt;Recreate the indices before restarting the search server by following the action in&amp;nbsp;&lt;a href="/support/w/kb/3550/kb-1082-issues-related-to-search-server-indices"&gt;KB-1082&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Start the search server.&lt;/li&gt;
&lt;li&gt;Start the application server.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed: &lt;span&gt;January 2025&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: administration, heap, search server, infrastructure&lt;/div&gt;
</description></item><item><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server/revision/5</link><pubDate>Wed, 10 Feb 2021 21:44:10 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6fd06938-333b-4e24-aecc-89e2140cc8a5</guid><dc:creator>Nicholas Van Dyke</dc:creator><comments>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server#comments</comments><description>Revision 5 posted to Appian Knowledge Base by Nicholas Van Dyke on 2/10/2021 9:44:10 PM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When utilizing functionality that requires the search server, the following error message is printed in the application server log:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Caused by: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], all shards failed; shardFailures {[90nFgyfMQPmYsbhzr2aI7w][xray-rule-execution][0]: ElasticsearchException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: UncheckedExecutionException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]; nested: ExecutionError[java.lang.OutOfMemoryError: Java heap space]; nested: OutOfMemoryError[Java heap space]; } 
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The error is seen when one of the search server functionalities requires more JVM heap than the configured maximum limit. By default, the search server will start with the configurations for initial and maximum memory usage (JVM heap) each set to 1024MB (1GB).&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Starting with Appian 17.2, rule performance metrics are aggregated every minute to help save on disk space and heap memory. Please upgrade to this version of Appian to help mitigate the heap issues in your environment.&lt;/p&gt;
&lt;h2&gt;Workaround&lt;/h2&gt;
&lt;p&gt;If upgrading to Appian 17.2 is not feasible, perform the following to manually increase the heap on the search server machine (&lt;strong&gt;Note:&lt;/strong&gt; The machine must be equipped to handle additional memory on the search server machine. Do not attempt these steps on a box that consistently runs high on memory):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Follow the steps mentioned in &lt;a href="https://docs.appian.com/suite/help/latest/Search_Server.html#Starting_and_Stopping"&gt;Starting and Stopping the Search Server&lt;/a&gt; to increase the search server heap limit.&lt;/li&gt;
&lt;li&gt;Stop the application server.&lt;/li&gt;
&lt;li&gt;Stop the search server.&lt;/li&gt;
&lt;li&gt;Recreate the indices before restarting the search server by following the action in&amp;nbsp;&lt;a href="/support/w/kb/306/kb-1082-issues-related-to-search-server-indices" rel="noopener noreferrer" target="_blank"&gt;KB-1082&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Start the search server.&lt;/li&gt;
&lt;li&gt;Start the application server.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed: &lt;span&gt;January 2021&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: administration, heap, search server, infrastructure&lt;/div&gt;
</description></item><item><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server/revision/4</link><pubDate>Thu, 09 Aug 2018 02:11:14 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6fd06938-333b-4e24-aecc-89e2140cc8a5</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server#comments</comments><description>Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 8/9/2018 2:11:14 AM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When utilizing functionality that requires the search server, the following error message is printed in the application server log:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Caused by: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], all shards failed; shardFailures {[90nFgyfMQPmYsbhzr2aI7w][xray-rule-execution][0]: ElasticsearchException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: UncheckedExecutionException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]; nested: ExecutionError[java.lang.OutOfMemoryError: Java heap space]; nested: OutOfMemoryError[Java heap space]; } 
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The error is seen when one of the search server functionalities requires more JVM heap than the configured maximum limit. By default, the search server will start with the configurations for initial and maximum memory usage (JVM heap) each set to 1024MB (1GB).&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Starting with Appian 17.2, rule performance metrics are aggregated every minute to help save on disk space and heap memory. Please upgrade to this version of Appian to help mitigate the heap issues in your environment.&lt;/p&gt;
&lt;h2&gt;Workaround&lt;/h2&gt;
&lt;p&gt;If upgrading to Appian 17.2 is not feasible, perform the following to manually increase the heap on the search server machine (&lt;strong&gt;Note:&lt;/strong&gt; The machine must be equipped to handle additional memory on the search server machine. Do not attempt these steps on a box that consistently runs high on memory):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Follow the steps mentioned in &lt;a href="https://docs.appian.com/suite/help/latest/Search_Server.html#Starting_and_Stopping"&gt;Starting and Stopping the Search Server&lt;/a&gt; to increase the search server heap limit.&lt;/li&gt;
&lt;li&gt;Stop the application server.&lt;/li&gt;
&lt;li&gt;Stop the search server.&lt;/li&gt;
&lt;li&gt;Recreate the indices before restarting the search server by following the action in&amp;nbsp;&lt;a href="/support/w/kb/306/kb-1082-issues-related-to-search-server-indices" target="_blank"&gt;KB-1082&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Start the search server.&lt;/li&gt;
&lt;li&gt;Start the application server.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed: August 2017&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: administration, heap, search server, infrastructure&lt;/div&gt;
</description></item><item><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server/revision/3</link><pubDate>Thu, 09 Aug 2018 02:10:50 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6fd06938-333b-4e24-aecc-89e2140cc8a5</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server#comments</comments><description>Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 8/9/2018 2:10:50 AM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When utilizing functionality that requires the search server, the following error message is printed in the application server log:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Caused by: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], all shards failed; shardFailures {[90nFgyfMQPmYsbhzr2aI7w][xray-rule-execution][0]: ElasticsearchException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: UncheckedExecutionException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]; nested: ExecutionError[java.lang.OutOfMemoryError: Java heap space]; nested: OutOfMemoryError[Java heap space]; } 
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The error is seen when one of the search server functionalities requires more JVM heap than the configured maximum limit. By default, the search server will start with the configurations for initial and maximum memory usage (JVM heap) each set to 1024MB (1GB).&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Starting with Appian 17.2, rule performance metrics are aggregated every minute to help save on disk space and heap memory. Please upgrade to this version of Appian to help mitigate the heap issues in your environment.&lt;/p&gt;
&lt;h2&gt;Workaround&lt;/h2&gt;
&lt;p&gt;If upgrading to Appian 17.2 is not feasible, perform the following to manually increase the heap on the search server machine (&lt;strong&gt;Note:&lt;/strong&gt; The machine must be equipped to handle additional memory on the search server machine. Do not attempt these steps on a box that consistently runs high on memory):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Follow the steps mentioned in &lt;a href="https://docs.appian.com/suite/help/latest/Search_Server.html#Starting_and_Stopping"&gt;Starting and Stopping the Search Server&lt;/a&gt; to increase the search server heap limit.&lt;/li&gt;
&lt;li&gt;Stop the application server.&lt;/li&gt;
&lt;li&gt;Stop the search server.&lt;/li&gt;
&lt;li&gt;Recreate the indices before restarting the search server by following the action in&amp;nbsp;&lt;a href="/support/w/kb/306/kb-1082-issues-related-to-search-server-indices" target="_blank"&gt;KB-1082&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Start the search server.&lt;/li&gt;
&lt;li&gt;Start the application server.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed: August 2017&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: heap, search server, infrastructure&lt;/div&gt;
</description></item><item><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server/revision/2</link><pubDate>Wed, 30 Aug 2017 08:42:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6fd06938-333b-4e24-aecc-89e2140cc8a5</guid><dc:creator>Nick Vigilante</dc:creator><comments>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server#comments</comments><description>Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 8/30/2017 8:42:35 AM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When utilizing functionality that requires the search server, the following error message is printed in the application server log:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Caused by: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], all shards failed; shardFailures {[90nFgyfMQPmYsbhzr2aI7w][xray-rule-execution][0]: ElasticsearchException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: UncheckedExecutionException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]; nested: ExecutionError[java.lang.OutOfMemoryError: Java heap space]; nested: OutOfMemoryError[Java heap space]; } 
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The error is seen when one of the search server functionalities requires more JVM heap than the configured maximum limit. By default, the search server will start with the configurations for initial and maximum memory usage (JVM heap) each set to 1024MB (1GB).&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Starting with Appian 17.2, rule performance metrics are aggregated every minute to help save on disk space and heap memory. Please upgrade to this version of Appian to help mitigate the heap issues in your environment.&lt;/p&gt;
&lt;h2&gt;Workaround&lt;/h2&gt;
&lt;p&gt;If upgrading to Appian 17.2 is not feasible, perform the following to manually increase the heap on the search server machine (&lt;strong&gt;Note:&lt;/strong&gt; The machine must be equipped to handle additional memory on the search server machine. Do not attempt these steps on a box that consistently runs high on memory):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Follow the steps mentioned in &lt;a href="https://docs.appian.com/suite/help/latest/Search_Server.html#Starting_and_Stopping"&gt;Starting and Stopping the Search Server&lt;/a&gt; to increase the search server heap limit.&lt;/li&gt;
&lt;li&gt;Stop the application server.&lt;/li&gt;
&lt;li&gt;Stop the search server.&lt;/li&gt;
&lt;li&gt;Recreate the indices before restarting the search server by following the action in&amp;nbsp;&lt;a href="/support/w/kb/306/kb-1082-issues-related-to-search-server-indices" target="_blank"&gt;KB-1082&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Start the search server.&lt;/li&gt;
&lt;li&gt;Start the application server.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed: August 2017&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: heap, search server&lt;/div&gt;
</description></item><item><title>KB-1125 Heap space issues with search server</title><link>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server/revision/1</link><pubDate>Fri, 24 Feb 2017 13:55:58 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6fd06938-333b-4e24-aecc-89e2140cc8a5</guid><dc:creator>Nick Vigilante</dc:creator><comments>https://community.appian.com/support/w/kb/347/kb-1125-heap-space-issues-with-search-server#comments</comments><description>Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/24/2017 1:55:58 PM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When utilizing functionality that requires the search server, the following error message is printed in the application server log:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Caused by: org.elasticsearch.action.search.SearchPhaseExecutionException: Failed to execute phase [query], all shards failed; shardFailures {[90nFgyfMQPmYsbhzr2aI7w][xray-rule-execution][0]: ElasticsearchException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: UncheckedExecutionException[org.elasticsearch.ElasticsearchException: java.lang.OutOfMemoryError: Java heap space]; nested: ElasticsearchException[java.lang.OutOfMemoryError: Java heap space]; nested: ExecutionError[java.lang.OutOfMemoryError: Java heap space]; nested: OutOfMemoryError[Java heap space]; } 
&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The error is seen when one of the search server functionalities requires more JVM heap than the configured maximum limit. By default, the search server will start with the configurations for initial and maximum memory usage (JVM heap) each set to 1024MB (1GB).&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;To correct this issue, perform the following:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Review &lt;a href="https://docs.appian.com/suite/help/17.1/Search_Server.html#Sizing"&gt;Search Server Sizing&lt;/a&gt; to determine how much JVM heap is required.&lt;/li&gt;
&lt;li&gt;Follow the steps mentioned in &lt;a href="https://docs.appian.com/suite/help/17.1/Search_Server.html#Starting_and_Stopping"&gt;Starting and Stopping the Search Server&lt;/a&gt; to increase the search server heap limit.&lt;/li&gt;
&lt;li&gt;Stop the application server.&lt;/li&gt;
&lt;li&gt;Stop the search server.&lt;/li&gt;
&lt;li&gt;Recreate the indices before restarting the search server by deleting &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/admin/search-local&lt;/code&gt;directory.&lt;/li&gt;
&lt;li&gt;Start the search server.&lt;/li&gt;
&lt;li&gt;Start the application server.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;February 2017&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: heap, search server&lt;/div&gt;
</description></item></channel></rss>