[Postgres-xl-bugs] Cluster running storec proc delivers different results depending on which coordinator you connect to

Gunther Thiel gunther at vatomic.io
Mon Dec 5 10:20:59 PST 2016


Hi guys,

I am running postgres-xl-9.5r1.3 and am experiencing a problem, when
executing a stored procedure. I have got 1 GTM, three coord and three dn's
running.
Depending on which coord I connect to, I am getting different results:

* coord1: Stored proc works fine
* coord2 and coord3: Same store proc being executed on the same stored proc
with same params and unchanged tables/data an error (ERROR:  no value found
for parameter 53).

Restarting the cluster does not provide a fix.

I guess it is related to the following errors in the GTM log.

(excerpted):

1:1879045888:2016-11-24 10:42:52.002 UTC -LOG:
GTM_ERRCODE_NODE_NOT_REGISTERED - node_name dn1

LOCATION:  GTM_HandleGlobalXmin, register_common.c:967

1:2449454848:2016-11-24 10:42:53.586 UTC -LOG:
GTM_ERRCODE_NODE_NOT_REGISTERED - node_name dn2

LOCATION:  GTM_HandleGlobalXmin, register_common.c:967

1:2432669440:2016-11-24 10:42:55.692 UTC -LOG:
GTM_ERRCODE_NODE_NOT_REGISTERED - node_name dn3

LOCATION:  GTM_HandleGlobalXmin, register_common.c:967

1:1879045888:2016-11-24 10:42:57.007 UTC -LOG:
GTM_ERRCODE_NODE_NOT_REGISTERED - node_name dn1

LOCATION:  GTM_HandleGlobalXmin, register_common.c:967

1:2449454848:2016-11-24 10:42:58.588 UTC -LOG:
GTM_ERRCODE_NODE_NOT_REGISTERED - node_name dn2

LOCATION:  GTM_HandleGlobalXmin, register_common.c:967

1:2432669440:2016-11-24 10:43:00.697 UTC -LOG:
GTM_ERRCODE_NODE_NOT_REGISTERED - node_name dn3

LOCATION:  GTM_HandleGlobalXmin, register_common.c:967

1:1879045888:2016-11-24 10:43:02.013 UTC -LOG:
GTM_ERRCODE_NODE_NOT_REGISTERED - node_name dn1

LOCATION:  GTM_HandleGlobalXmin, register_common.c:967


Here is now my questions, if I may:

a) How can I get rid of these errors?

b) Are they the root cause for my stored proc function?

c) Will upgrading to r4 maybe fix this (I did not see anything that jumped
on me when reading the commit log).


Thanks for any input.

Gunther


P. S.: If anyone needs to see details about the tables, stored proc etc, I
am happy to provide it but I guess it might not be needed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/private.cgi/postgres-xl-bugs-postgres-xl.org/attachments/20161205/b62806e0/attachment.htm>


More information about the postgres-xl-bugs mailing list