queue_poison_pill table missing PK

[sych74]

The queue_poison_pill table is missing a PK. Because of this, it cannot be replicated reliably in Galera based systems (eg. MariaDB, Percona XtradbCluster).

Preconditions (*)

Magento 2.4.3

Steps to reproduce (*)

1. Open database table queue_poison_pill
2. Check if the table has a Primary Key

Expected result (*)

The database table queue_poison_pill has Primary Key

Actual result (*)

The database table queue_poison_pill doesn't have Primary Key

SQLSTATE[42000]: Syntax error or access violation: 1173 This table type requires a primary key, query was: 
CREATE TABLE `queue_poison_pill` ( `version` varchar(255) NOT NULL  COMMENT "Poison Pill version.") 
ENGINE=innodb DEFAULT CHARSET=utf8 DEFAULT COLLATE=utf8_general_ci COMMENT="Sequence table for poison pill versions"

[m2-assistant]

Hi @sych74. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Echo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Echo]

Hi @sych74
Thanks for reporting the issue.
We checked on your issue. The queue_poison_pill table will always have a single version entry, which is basically just a random hash. If some configuration value gets changed using the Magento backend, the poison pill version is changed. The running consumer processes check on this version, but only when a new message is in the queue. So in this case we have a natural key version that hold the single unique entry.
In code base the version is treated as the idFieldName.
protected function _construct()
{
$this->_init(self::QUEUE_POISON_PILL_TABLE, 'version');
}

If you have faced any issues/errors w.r.t to this table not having an explicit PK, please write to us , with actual steps to reproduce the issue, expected & actual results. We shall definitely look into the same.

Thank you.

[engcom-Hotel]

Dear @sych74,

We have noticed that this issue has not been updated for a period of more than 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Regards

[siliconalchemy]

@engcom-Echo - the problem is that this missing PK prevents Magento from installing or operating correctly on a Galera based cluster, such as Percona Xtradb Cluster. Galera is a very popular replication system for Mysql, and is widely used for mission critical environments such as Magento.

During install, it fails with this error:

[Progress: 661 / 1323]
Installing user configuration...

In Mysql.php line 109:

  SQLSTATE[HY000]: General error: 1105 Percona-XtraDB-Cluster prohibits use of DML command on a table (net_siliconalchemy_magento2.queue_poison_pil
  l) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER, query was: INSERT INTO `queue_poison_pill` (`version`) VALUES (?)


In Mysql.php line 90:

  SQLSTATE[HY000]: General error: 1105 Percona-XtraDB-Cluster prohibits use of DML command on a table (net_siliconalchemy_magento2.queue_poison_pil
  l) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER

[Tanguy-hthai]

Same there, I have this error on an Aurora DB:
ERROR 3750 (HY000) at line 12288: Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.

At line 12288, I have the SQL query to create the queue_poison_pill table.

[engcom-Hotel]

Hello @Lathanao,

The similar issue has been confirmed already:

#39239

Please refer to that issue for the updates.

Thanks