Planet MySQL

Planet MySQL -
  1. I had the pleasure to receive a nice educative video from my colleague Narendra Singh Chauhan, working in the QA team for MySQL Replication. If you are curious to understand how all this works, please take a look at the video, like it and share it
  2. As announce on Oct 18, 2018 we would like to just remind about the Open Source Conference in Tokyo, Japan which will be hold tomorrow, December 14, 2018. Please come to hear the MySQL talk on "State of Dolphin" by Yoshiaki Yamasaki, the MySQL Senior Sales Consultant Asia Pacific and Japan region. During his talk the general product updates will be covered. You can also find our team at the MySQL booth in the expo area. We are looking forward to seeing and talking to you at this show!  
  3. Continuent is pleased to announce that Continuent Clustering 6.0.4 and Tungsten Replicator 6.0.4 are now available! Our v6.0.4 release fixes a number of bugs and introduces some new features, with improvements across the board in a variety of different components. Some of the key improvements include: When installing from an RPM, the installation would automatically restart the Connector during the installation. This behavior can now be controlled by setting the parameter --no-connectors within the configuration to prevent tpm from restarting the Connectors during the automated update processing. Cross-site Replicators within a composite multimaster deployment can now be configured to point to slaves by default, and to prefer slaves over masters during operation using the new --policy-relay-from-slave=true option You can now enable an option so that when a site comes back online, the Connector will disconnect all connections that couldn’t get to their preferred site so that they will then reconnect to the expected site with the appropriate affinity (--connector-reset-when-affinity-back=true) Some of the highlights common to both products: When using tpm diag, the command would fail to parse net-ssh options The Net::SSH internal options have been updated to reflect changes in the latest Net::SSH release Fixes specific to Continuent Clustering: When performing a tpm update in a cluster with an active witness, ensure that the host with the witness is restarted correctly In a composite multimaster deployment, once a datasource has been welcomed to the cluster, ensure that individual clusters within the composite agree on the overall state of all clusters Because long service names can cause formatting issues, a new option, --cctrl-column-width has been added which can be used to configure the minimum column width used to display information The Connector has been modified to get the driver and JDBC URL of the datasource from the Connector-specific configuration, overriding the information normally distributed to it by the manager. This prevents the Connector from using incorrect settings, or empty values. Ensure that datasources are fenced correctly when a Replicator fails Ensure that standby datasources are displayed within cctrl correctly Fixes specific to Tungsten Replicator: The trepctl command previously required the -service option to be the first option on the command-line. The option can now be placed in any position on the command-line. If no service is specified then using trepctl and multiple services are configured, then an error would be reported, but no list of potential services would be provided. This has been updated so that trepctl will output the list available services and potential commands. Heartbeats would be inserted into the replication flow using UTC even if the Replicator had been configured to use a different timezone Full release notes are available:
  4. At AWS Re:Invent 2018 there were many great announcements of AWS New Services and New Features, but one basic feature that I’ve been waiting for years to be released is still nowhere to be  found. AWS Elastic Block Storage (EBS) is great and it’s got better through the years, adding different storage types and features like Provisioned IOPS. However, it still has the most basic inconvenient requirement – I have to decide in advance how much space I need to allocate, and pay for all of that allocated space whether I use it or not. It would be so much better if AWS would allow true consumption model pricing with EBS, where you pay for the storage used, not the storage allocated. This is already the case for S3,  RDS, and even EC2 instances (with Unlimited Option on T2/T3 Instances), not to mention Serverless focused services. For example, I would love to be able to create a 1TB EBS volume but only pay for 10GB of storage if I only use this amount of space. Modern storage subsystems do a good job differentiating between the space available on the block device and what’s being used by user files and filesystem metadata. The space that’s not allocated any more can be TRIMmed. This is a basic requirement for working well on flash storage, and as modern EC2 instances already provision EBS storage as emulated NVMe devices, I would imagine Amazon could hook into such functionality to track space actually used. For us at Percona this would make shipping applications on AWS Marketplace much more convenient. Right now for Percona Monitoring and Management (PMM)  we have to choose how much space to allocate to the EBS volume by default, picking between it being expensive to run because of paying for the large unused EBS volume or setting a very limited by default capacity that needs user action to resize the EBS volume. Consumption-based EBS pricing would solve this dilemma. This problem seems to be well recognized and understood. For example Pure Storage Cloud Block Storage (currently in Beta) is  expected to have such a feature. I hope with its insane customer focus AWS will add this feature in the future, but currently we have to get by without it. —Image: Arnold Reinhold [CC BY-SA 2.5], via Wikimedia Commons
  5. Please join Percona’s CEO Peter Zaitsev as he presents MySQL 8 for Developers on Wednesday, December 12th, 2018 at 11:00 AM PST (UTC-7) / 2:00 PM EST (UTC-5). Register Now There are many great new features in MySQL 8, but how exactly can they help your application? This session takes a practical look at MySQL 8 features. It also details which limitations of previous MySQL versions are overcome by MySQL 8. Lastly, what you can do with MySQL 8 that you could not have done before is discussed. Register for MySQL 8 for Developers to learn how MySQL’s new features can help your application and more.