question Re: Hive Error : Postgres: intermittent test failure due to "ERROR: could not serialize access due to read/write dependencies among transactions" in Archives of Support Questions (Read Only)

Hive Error : Postgres: intermittent test failure due to "ERROR: could not serialize access due to read/write dependencies among transactions"

raghusiddarth — Mon, 08 Aug 2016 22:45:14 GMT

Hello, I'm getting the above error in Hive, which as per the HDP release notes, seems to be a know issue : http://dev.hortonworks.com.s3.amazonaws.com/HDPDocuments/HDP2/HDP-2.2.6/HDP_RelNotes_v226/content/ref-4b2a1f7a-c423-4352-be22-1ab0f7594dce.1.html

This is the bug :

BUG-27637

Postgres: intermittent test failure due to "ERROR: could not serialize access due to read/write dependencies among transactions"

Hive

But I'm not able to find details about this bug, which issue tracker do I check for the details?

Re: Hive Error : Postgres: intermittent test failure due to "ERROR: could not serialize access due to read/write dependencies among transactions"

agillan — Mon, 08 Aug 2016 22:57:03 GMT

Hi @Raghu Udiyar that BUG ID is a Hortonworks internal ID which corresponds to Apache JIRA HIVE-10500

That particular bug has been "backported" to previous versions of Hive in the HDP distribution, so it is fixed in HDP versions 2.2.6 and higher.

Re: Hive Error : Postgres: intermittent test failure due to "ERROR: could not serialize access due to read/write dependencies among transactions"

raghusiddarth — Tue, 09 Aug 2016 01:10:07 GMT

Ok, Thanks! I'm on HDP 2.2.9, so this should be fixed then. The change log has Apache Jira for some, but not all of the change logs, having Apache Jira ids would really help.

Re: Hive Error : Postgres: intermittent test failure due to "ERROR: could not serialize access due to read/write dependencies among transactions"

raghusiddarth — Tue, 09 Aug 2016 01:31:07 GMT

@Ana Gillan We are seeing this error on HDP 2.2.9 when we run to storm hive bolts in parallel. The error goes away when a single bolt is used. Is this expected behaviour?