Options
8.1.x memory leak
We are running 8.1.x AMI, CentOS on Redhat 7.3 with glibc version 2.17-157.el7_3.1. We have been running 7.2.x succesful more months. Now after just a few hours we get killed by OOM-Killer.
We experienced a similar issue back 7.x and rolled back to an old glibc version. However, everyone has assured us that this is the recommendation configuration in AWS.
Anyone else experience this?
0
Comments
We have been plagued with OOM issues. Just had two nodes go down today within 15 minutes of each other, not good.
I posted about this at:
https://forum.vertica.com/discussion/239301/vertica-8-1-1-oom-constantly-getting-killed
Were you able to figure out the issue?
Hi,
What version of Vertica are you guys using? Below is a list of hot fixes for memory/resource manager issues.
Note that we recommend to be at release 8.1.1-9 in the 8.1.x release stream. See: https://forum.vertica.com/discussion/comment/240019#Comment_240019
Hot fixes in 8.1.x:
VERSION ISSUE COMPONENT DESCRIPTION
8.1.1-10 (12/12/2017) VER-59121 Resource Manager, Security After being granted usage and select privileges on a schema and table in a specific resource pool, the user was denied permission when trying to access the schema and table. This was because Vertica was checking permissions on secondary resource pools.
8.1.1-9 (11/14/2017) VER-58838 Catalog Engine The Vertica garbage collector algorithm has been modified to prevent query slowdown.
8.1.1-6 (09/27/2017) VER-57030 Catalog Engine Vertica did not previously release the catalog memory for objects that were no longer visible by any current or subsequent transactions. The Vertica garbage collector algorithm has been improved.
8.1.1-0 (07/10/2017) VER-52834 Catalog Engine In rare cases, updating a table that had failed to commit caused an assertion due to incomplete catalog cleanup.
8.1.1-0 (07/10/2017) VER-53843 Catalog Engine Vertica previously stored full width padded strings as max values, resulting in unnecessarily large catalogs that could cause node failure.
8.1.0-5 (07/07/2017) VER-54667 Catalog Engine Vertica previously stored full width padded strings as max values, resulting in unnecessarily large catalogs that could cause node failure.
8.1.0-4 (06/08/2017) VER-54522 Catalog Engine, ResourceManager During recovery, if acquiring a global catalog lock failed on some nodes, the nodes sometimes panicked and aborted recovery.
8.1.0-0 (04/13/2017) VER-34605 Catalog Engine Previously, the view_definition column of the VIEWS system table would truncate definitions that exceeded the 8192 character limit. The limit for the view_definition column has been increased to 65,000 characters.
8.1.0-0 (04/13/2017) VER-48469 ResourceManager In some circumstances, Vertica continually allocated unused virtual memory, which slowed performance. This issue has been resolved.