Bug 1311409 - IJ000460: Error checking for a transaction error happened.
Summary: IJ000460: Error checking for a transaction error happened.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 08:02 UTC by Yoshinori Takahashi
Modified: 2019-10-10 11:22 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-31 05:40:47 UTC
oVirt Team: Infra
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 2 Tomas Jelinek 2016-02-24 11:46:53 UTC 
Arik, could you please check?
Comment 3 Arik 2016-02-25 08:31:10 UTC 
Yoshinori, please attach engine log
Comment 5 Arik 2016-02-25 09:32:02 UTC 
Different queries, in different flows, fail with exactly the same exception - seems like a general problem with the interaction with the database.

Yoshinori, can you please attach server.log as well? maybe it will hint the cause for this.
Comment 6 Tomas Jelinek 2016-03-02 08:55:34 UTC 
@Yoshinori after you have restarted the engine, did the issue disappear? Is this issue reproducing to you constantly or it happened only once?
Comment 10 Tomas Jelinek 2016-03-03 09:12:02 UTC 
@Martin: any idea what could lead to this?
Comment 12 Tomas Jelinek 2016-03-07 08:01:40 UTC 
It seems as an more generic infra issue - moving to the right component.
Comment 19 Martin Perina 2016-03-23 11:22:15 UTC 
Hi,

the defaults for maxThreads (max-connection option in config file) are described at [4], so it should be:

  512 * number of processors in engine server


[4] https://access.redhat.com/solutions/25054
Comment 20 Martin Perina 2016-03-30 08:19:23 UTC 
Hi,

any progress with the investigation of overload?
Note You need to log in before you can comment on or make changes to this bug.