We have read only scale out with one root node and two children. I'me inserting rows with following statement into table customer.

BEGIN
DECLARE i INTEGER;
SET i = 1;
WHILE 1=1 LOOP
   SET i = i + 1;
  INSERT INTO customer VALUES 
(i,'zzzr','N','xxx','2016-10-19 05:57:16.152','fsafsdg',
'2001-10-31',NULL,1,'mm-dd-yyyy','mm-dd-yyyy',6,2,NULL,'N',NULL,'12.1',i+2000);
END LOOP;
END

and I discovered unexpected behavior. If I'm inserting rows in existing table customer they are not available before commit at child ROSO node(from other transaction). So I'm getting behavior like snapshot read-only isolation level. After commit data are persisted and visible.

I created copy of customer table named customer1 and If I'm inserting rows in table customer1 they are available before commit at child ROSO node(from other transaction). So I'm getting behavior like dirty read isolation level.

Maybe I'm missing something. What could cause this behavior ?

asked 07 Nov '16, 03:55

maros000's gravatar image

maros000
56117
accept rate: 0%

1

What does "call sa_mirror_server_status()" reveal in both cases?

(07 Nov '16, 05:43) Volker Barth
Replies hidden

In both cases sa_mirror_server_status( ) read only nodes status is 'connected' and log_written = log_applied

(07 Nov '16, 06:11) maros000

I got it ! :)

That DB is migrated to SA16 from SA11 before there has been replications and existing table is in publications. If table IS in publication, rows are not sent to children and I'm getting like 'snapshot read-only isolation level'. If table IS NOT in publication rows are sent and visible(dirty reads as expected). For now I considered it as bug. I don't see reasons why there should be relation between publication and read only scale out.

Should I tried to open bug ticket for it ?

permanent link

answered 07 Nov '16, 07:42

maros000's gravatar image

maros000
56117
accept rate: 0%

1

If you feel it is a bug you should open a ticket.

(07 Nov '16, 07:46) Martin
Replies hidden

... and later please tell us about the outcome.

(09 Nov '16, 03:22) Vlad

Did you check the UncommitOp connection property of your insert session to verify that the changes really were pending?

What's the isolation level of your ROSO session?

permanent link

answered 07 Nov '16, 06:44

Volker%20DB-TecKy's gravatar image

Volker DB-TecKy
256249
accept rate: 33%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×3

question asked: 07 Nov '16, 03:55

question was seen: 430 times

last updated: 09 Nov '16, 03:22