When trivial provider is loaded, setting 'wsrep_cluster_address' should return error

Bug #815522 reported by Alex Yurchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Confirmed
Medium
Alex Yurchenko

Bug Description

mysql> set global wsrep_cluster_address='gcomm://192.168.0.102';
Query OK, 0 rows affected (2.00 sec)

mysql> show variables like 'wsrep_provider';
+----------------+-------+
| Variable_name | Value |
+----------------+-------+
| wsrep_provider | none |
+----------------+-------+
1 row in set (0.00 sec)

It confuses the operator, making him to think that connection to cluster was successful.

Changed in codership-mysql:
assignee: nobody → Alex Yurchenko (ayurchen)
importance: Undecided → Medium
milestone: none → 0.8.2
status: New → Confirmed
Changed in codership-mysql:
milestone: 0.8.2 → 0.8.3
Changed in codership-mysql:
milestone: 0.8.3 → 5.1.57-21.1
Revision history for this message
Yan Zhang (yan.zhang) wrote :

I think trivial provider should act like black hole swallow everything without feedback.

Revision history for this message
Alex Yurchenko (ayurchen) wrote :

On one hand it should.
On the other, failure to load the provider may go unnoticed (e.g. API mismatch) and this is the way to notify the user that wsrep functionality is in fact missing.
Also, loading a proper provider will zero up wsrep_cluster_address and wsrep_provider_options set while the dummy provider was loaded. So returning error when user attempts to set any of these should indicate to him that these actions will have no result and he will have to repeat them after loading a proper provider.

Revision history for this message
Alex Yurchenko (ayurchen) wrote :

Just to clarify - here we distinguish between setting provider-specific variables and regular database operations. Ideally, wsrep_% variables should not be visible at all when provider is not loaded - compare that to InnoDB variables which are not visible when InnoDB is disabled - but that's a far bigger task.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.