Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 50 million developers.
Sign upBUG#31945539 LOADING DUMPS WITH CHUNKS LARGER THAN TRANSACTION LIMIT … …FAILS When a chunk file has more data than would fit in a single transaction, as limited by configurations like group_replication_transaction_size_limit or max_binlog_cache_size, the LOAD DATA would fail with an error. The problem is compounded by the fact that certain tables can end up with chunks that are much larger than the specified bytesPerChunk value, no matter how small that value is set. This patch works around that by flushing out chunks during load (by prematurely ending the LOAD DATA operation at a whole row boundary), whenever the number of bytes sent is about to go over bytesPerChunk * 1.5 bytes. LOAD DATA is then re-issued to load the rest of the file. Also: Store bytesPerChunk used during dump in the dump metadata, along with the uncompressed chunk file sizes in @.done.json Increased default bytesPerChunk to 64M since impact of over-sized chunks is now reduced, while still accounting for relatively small values of group_replication_transaction_size_limit. Change-Id: I890124f92487269c8b7c650de60c0a9d1c446431
BUG#28915716 MEMSET IS NOT A PROPER FUNCTION TO ERASE SENSITIVE DATA The buffers used to temporarily store the passwords obtained from the user were not being properly cleaned, in some cases memset was being used to "cleanup" the buffers and in other cases not even that. memset may be optimized away (under the as-if rules) if the object modified by this function is not accessed again for the rest of its lifetime, letting the password data available in the memory buffer. This patch replaces memset with functions that are excluded by this optimization, explicit_bzero in linux and SecureZeroMemory in windows eliminating the potential risk. Change-Id: Ia5c401db5d9eaea3f8e2b31aabc922930a08f2c8
BUG#27677227 SILENT ASSUMPTION WHEN CONFIGURING CLUSTER WITH X PROTOC… …OL DISABLED When a cluster is created on a server that doesn't have the X Plugin enabled, a silent assumption is made about the X Protocol port value. The port value is calculated based on a default assumption that the X Protocol port is equal to value of the classic protocol * 10. Such value in stored in the metadata schema under the addresses column of the instances table, having the value of 'mysqlX'. Such assumption cannot be done and the address information related to the X Protocol should only be stored under 'mysqlX' if the protocol is enabled. This patch fixes the issue by making sure that the value of 'mysqlX' is only stored for instances on which the X Protocol is enabled. Otherwise no value is stored. Added unit-tests for regression. Change-Id: I4081eaf2f83dbe83682663b13f8d3777df9d5d0b (cherry picked from commit e361a44c5197ac2c3767a2cbaa5ff62510766517)
PreviousNext
