<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Poor performance/errors when accessing SAS Viya apps due to high memory or disk space in RabbitMQ in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Poor-performance-errors-when-accessing-SAS-Viya-apps-due-to-high/m-p/943495#M29019</link>
    <description>&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Issue: &lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;SAS has recently identified and remediated an issue reported in SAS Viya LTS 2024.04 and Stable 2024.05-Stable 2024.08. For customers running those versions, visit the &lt;/SPAN&gt;&lt;A href="https://sas.service-now.com/csm?id=kb_article&amp;amp;sys_id=06a069a58360d6949c65bddfeeaad393" target="_blank" rel="noopener"&gt;&lt;SPAN data-contrast="none"&gt;SAS Support Knowledge Base&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN data-contrast="auto"&gt; for ways to identify orphaned RabbitMQ orphaned queues, as well as remediation steps.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Background:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; After upgrading recent releases of SAS Viya, some RabbitMQ queues might become orphaned. An orphaned queue means that no application is consuming messages from the queue. The queue will not be deleted, causing RabbitMQ pods to consume more memory as messages are added to the queue.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The RabbitMQ pods might be OOMKilled by Kubernetes continuously, causing the RabbitMQ container to restart. This issue can impact the stability of the SAS Viya system, including errors when starting new jobs or compute sessions, along with general slowness when accessing the SAS Viya applications.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An article on &lt;/SPAN&gt;&lt;A href="https://sas.service-now.com/csm?id=kb_article&amp;amp;sys_id=06a069a58360d6949c65bddfeeaad393" target="_blank" rel="noopener"&gt;&lt;SPAN data-contrast="none"&gt;SAS Support Knowledge Base&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN data-contrast="auto"&gt; provides detailed experience on how to identify and resolve these issues.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Sep 2024 16:47:29 GMT</pubDate>
    <dc:creator>ChrisHemedinger</dc:creator>
    <dc:date>2024-09-11T16:47:29Z</dc:date>
    <item>
      <title>Poor performance/errors when accessing SAS Viya apps due to high memory or disk space in RabbitMQ</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Poor-performance-errors-when-accessing-SAS-Viya-apps-due-to-high/m-p/943495#M29019</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Issue: &lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;SAS has recently identified and remediated an issue reported in SAS Viya LTS 2024.04 and Stable 2024.05-Stable 2024.08. For customers running those versions, visit the &lt;/SPAN&gt;&lt;A href="https://sas.service-now.com/csm?id=kb_article&amp;amp;sys_id=06a069a58360d6949c65bddfeeaad393" target="_blank" rel="noopener"&gt;&lt;SPAN data-contrast="none"&gt;SAS Support Knowledge Base&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN data-contrast="auto"&gt; for ways to identify orphaned RabbitMQ orphaned queues, as well as remediation steps.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Background:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; After upgrading recent releases of SAS Viya, some RabbitMQ queues might become orphaned. An orphaned queue means that no application is consuming messages from the queue. The queue will not be deleted, causing RabbitMQ pods to consume more memory as messages are added to the queue.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The RabbitMQ pods might be OOMKilled by Kubernetes continuously, causing the RabbitMQ container to restart. This issue can impact the stability of the SAS Viya system, including errors when starting new jobs or compute sessions, along with general slowness when accessing the SAS Viya applications.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ccp-props="{&amp;quot;201341983&amp;quot;:0,&amp;quot;335559739&amp;quot;:0,&amp;quot;335559740&amp;quot;:240}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An article on &lt;/SPAN&gt;&lt;A href="https://sas.service-now.com/csm?id=kb_article&amp;amp;sys_id=06a069a58360d6949c65bddfeeaad393" target="_blank" rel="noopener"&gt;&lt;SPAN data-contrast="none"&gt;SAS Support Knowledge Base&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN data-contrast="auto"&gt; provides detailed experience on how to identify and resolve these issues.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2024 16:47:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Poor-performance-errors-when-accessing-SAS-Viya-apps-due-to-high/m-p/943495#M29019</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2024-09-11T16:47:29Z</dc:date>
    </item>
  </channel>
</rss>

