spew every 1000 send/received remtran#5805
Conversation
roborivers
left a comment
roborivers
left a comment
There was a problem hiding this comment.
Cbuild submission: Success ✓.
Regression testing: Success ✓.
The first 10 failing tests are:
writes_remsql_names_rte_connect_generated [core dumped]
writes_remsql_names_partial_index_off_generated [core dumped]
writes_remsql_names_fdbpushredirect_generated [core dumped]
writes_remsql_names_negativerowid_generated [core dumped]
writes_remsql_names_fdbpush_generated [core dumped]
writes_remsql_names [core dumped]
sc_resume_logicalsc_generated
cldeadlock
consumer_non_atomic_default_consumer_generated
truncatesc_offline_generated
Signed-off-by: Dorin Hogea <dhogea@bloomberg.net>
dorinhogea
force-pushed
the
trackremtran
branch
from
8e62462 to
d969eb6
Compare
roborivers
left a comment
roborivers
left a comment
There was a problem hiding this comment.
Cbuild submission: Success ✓.
Regression testing: Success ✓.
The first 10 failing tests are:
sc_truncate_multiddl_generated
consumer_non_atomic_default_consumer_generated
remsql_locks_rte_connect_generated
remsql_locks
|
@mponomar thank you! |
3 participants
this will let us detect the cases when a new server talk to a legacy server requiring remtran ("SENDING REMTRAN" alert). it will also let us know when a new server receives a legacy remtran from an older server ("RECEIVED REMTRAN" alert).
Preamble to remove remtran protocol