Improved handling of different member versions in Group Replication

For optimal compatibility and performance, all members of a group should run the same version of MySQL Server and therefore of Group Replication. However, in some situations, it may be required to that a group contains servers running different versions. For example, during a rolling upgrade. When different versions exist Continue Reading

Zegost from Within – New Campaign Targeting Internal Interests

Adversary Playbook: The FortiGuard SE Team is releasing this new playbook on the threat actor group named Yet Another Panda as part of our role in the Cyber Threat Alliance. For more information regarding this series of adversary playbooks being created by CTA members, please visit the Cyber Threat Alliance Continue Reading

Undocumented Excel Variable Used in Malicious Spam Run Targeting Japanese Users

Over the course of the past few months, the FortiGuard SE group has been utilizing and enhancing the Fortinet machine learning systems to detect emerging threats. Recently, one of those machines detected an anomalous spike that led us to discover a malware campaign that had been using social engineering techniques Continue Reading

GandCrab Threat Actors Retire…Maybe

In a surprising announcement two weeks ago, the threat group behind the malware operation GandCrab announced that they had shut down their operations. Until that point, GandCrab had been one of the most active malware campaigns of the past year, both in terms of distribution and rapid development. FortiGuard Labs Continue Reading

No Ping Will Tear Us Apart – Enabling member auto-rejoin in Group Replication

With the release of version 8.0.16 of MySQL, we’ve added some features to the Group Replication (GR) plugin, in order to enhance its high-availability capacities. One of these features was the ability to enable a member that has left the group, under certain circumstances, to automatically rejoin it, without need Continue Reading

Change group_replication_exit_state_action default option to READ_ONLY

In MySQL 8.0.16, the Group Replication plugin variable group_replication_exit_state_action default value has been changed to READ_ONLY. The group_replication_exit_state_action plugin variable was introduced in MySQL 8.0.12 to allow the user to configure how Group Replication behaves when a server instance leaves the group unintentionally. The group_replication_exit_state_action has following two values: ABORT_SERVER: Continue Reading

Silence Group Playbook

Adversary Playbook: The FortiGuard SE Team is releasing this new playbook on the threat actor group known as Silence Group as part of our role in the Cyber Threat Alliance. For more information regarding this series of adversary playbooks being created by CTA members, please visit the Cyber Threat Alliance Playbook Continue Reading

Group Replication – Consistent Reads Deep Dive

On previous posts about Group Replication consistency we: introduced consistency levels; explained how to configure the primary failover consistency; presented how to configure transaction consistency levels to achieve the consistency required by your applications. In blog 3. we presented the consistency levels: EVENTUAL, BEFORE, AFTER and BEFORE_AND_AFTER; their scopes: SESSION, Continue Reading

IPv6 support in Group Replication

In 8.0.14, we add to Group Replication (GR) the ability to use IPv6 in all of its network-related configuration parameters. This means that now you can take advantage of this technology and “rock” those billion addresses using MySQL Group Replication. What’s New When you operate a Group Replication group, some Continue Reading

Fail early, fail fast – preventing stale reads on a member that dropped out of the group!

In Group Replication, starting with MySQL 8.0.12, the user is able to specify the behavior for members that enter an error state. The member can either shoot itself on the head or set itself to read-only. But what does that mean in practice? This blog post will give you a Continue Reading

>