This was resolved (for us) in:
Resolved issues in Vertica 7.0.1-2
VER-31016 (Execution Engine) Certain queries involving Group By where the data was partially sorted could result in a server crash. This issue has been resolved.
Search found 4 matches
- Mon Jul 21, 2014 9:33 am
- Forum: Vertica Premium Edition
- Topic: SEGV_ACCERR in GroupByHash running v7.0.0-1
- Replies: 1
- Views: 58204
- Mon Feb 03, 2014 4:41 pm
- Forum: Vertica Premium Edition
- Topic: SEGV_ACCERR in GroupByHash running v7.0.0-1
- Replies: 1
- Views: 58204
SEGV_ACCERR in GroupByHash running v7.0.0-1
SEGV_ACCERR in GroupByHash running v7.0.0-1 VER_7_0_RELEASE_BUILD_0_1_20131219@127765 Hello and thanks for vertica-forums, On a 6 node cluster running on RHEL6.4 (on unsupported LVM), one node crashed, from the error log: 2014-02-03 08:41:30.205 EEcmdq:0xabf7a40 [Main] <PANIC> Received fatal signal ...
- Fri Jun 28, 2013 4:17 pm
- Forum: New to Vertica Database Administration
- Topic: CPU frequency scaling
- Replies: 3
- Views: 9462
Re: CPU frequency scaling
See: https://my.vertica.com/docs/6.1.x/HTML/index.htm#18481.htm it is very much dependent on the hardware (CPUs and BIOS (you may want to check BIOS release notes for any fixes for C-states , C1E , P-states , Dynamic frequency scaling , CPU throttling , Dynamic voltage scaling , Advanced Configurati...
- Fri Jun 28, 2013 3:32 pm
- Forum: New to Vertica Database Administration
- Topic: agentStdMsg.log errors from inotify.py open StorageInfoByMin
- Replies: 0
- Views: 3773
agentStdMsg.log errors from inotify.py open StorageInfoByMin
Subject: agentStdMsg.log full of errors from inotify.py from trying to open DataCollector/StorageInfoByMinute_*.log files that do not exist. While running vertica-6.1.1-0.x86_64 on RedHat EL6.3 2.6.32-279.19.1.el6.x86_64 I noticed the gentStdMsg.log is full of errors from inotify.py, for example: Tr...