Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
6b018a16
Commit
6b018a16
authored
Nov 06, 2007
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bug #31484 Cluster LOST_EVENTS entry not added to binlog on mysqld restart
- correction, do not insert GAP on first startup
parent
ea9b647d
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
20 additions
and
2 deletions
+20
-2
sql/ha_ndbcluster_binlog.cc
sql/ha_ndbcluster_binlog.cc
+20
-2
No files found.
sql/ha_ndbcluster_binlog.cc
View file @
6b018a16
...
@@ -3725,8 +3725,25 @@ restart:
...
@@ -3725,8 +3725,25 @@ restart:
/*
/*
Main NDB Injector loop
Main NDB Injector loop
*/
*/
if
(
ndb_binlog_running
)
while
(
ndb_binlog_running
)
{
/*
check if it is the first log, if so we do not insert a GAP event
as there is really no log to have a GAP in
*/
{
LOG_INFO
log_info
;
mysql_bin_log
.
get_current_log
(
&
log_info
);
int
len
=
strlen
(
log_info
.
log_file_name
);
uint
no
=
0
;
if
((
sscanf
(
log_info
.
log_file_name
+
len
-
6
,
"%u"
,
&
no
)
==
1
)
&&
no
==
1
)
{
{
/* this is the fist log, so skip GAP event */
break
;
}
}
/*
/*
Always insert a GAP event as we cannot know what has happened
Always insert a GAP event as we cannot know what has happened
in the cluster while not being connected.
in the cluster while not being connected.
...
@@ -3739,8 +3756,9 @@ restart:
...
@@ -3739,8 +3756,9 @@ restart:
IF_DBUG
(
int
error
=
)
IF_DBUG
(
int
error
=
)
inj
->
record_incident
(
thd
,
INCIDENT_LOST_EVENTS
,
msg
[
incident_id
]);
inj
->
record_incident
(
thd
,
INCIDENT_LOST_EVENTS
,
msg
[
incident_id
]);
DBUG_ASSERT
(
!
error
);
DBUG_ASSERT
(
!
error
);
incident_id
=
1
;
break
;
}
}
incident_id
=
1
;
{
{
thd
->
proc_info
=
"Waiting for ndbcluster to start"
;
thd
->
proc_info
=
"Waiting for ndbcluster to start"
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment