Hi
user
Admin Login:
Username:
Password:
Name:
Crash-safe Replication with MariaDB and MySQL Global Transaction ID.
--client
osdc
--show
osdc2015
--room Riviera 10383 --force
Next: 1 Hack the Planet - A practical guide to web application vulnerabilities
show more...
Marks
Author(s):
Peter Lock
Location
Riviera
Date
oct Tue 27
Days Raw Files
Start
13:40
First Raw Start
error-in-template
Duration
00:130:00
Offset
None
End
15:50
Last Raw End
Chapters
Total cuts_time
None min.
http://2015.osdc.com.au/schedule/presentation/12/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Crashsafe_Replication_with_MariaDB_and_MySQL_Global_Transaction_ID.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
Traditional MySQL/MariaDB replication has difficulties when repointing a slave from one master to another. And if the slave crashes, it can lose its place in the replication stream. But recent versions have implemented Global Transaction IDs, to fix these problems. Let's have a go!
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review