Comment 6 for bug 1330941

I tried this with latest version from trunk and here is what I see.

1. Started 2 node cluster node-1 and node-2

2. Workload running on node-1

mysql> create table test (a int);
Query OK, 0 rows affected (0.04 sec)

mysql> set global wsrep_osu_method=rsu;
Query OK, 0 rows affected (0.00 sec)

mysql> set global wsrep_desync=off;
ERROR 1231 (42000): Variable 'wsrep_desync' can't be set to the value of 'OFF'
mysql> alter table test add index (a);
Query OK, 0 rows affected (0.05 sec)
Records: 0 Duplicates: 0 Warnings: 0

mysql> set global wsrep_desync=on;
Query OK, 0 rows affected (0.01 sec)

mysql> alter table test add index (a);
Query OK, 0 rows affected, 1 warning (0.07 sec)
Records: 0 Duplicates: 0 Warnings: 1

mysql> show warnings;
+-------+------+------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+-------+------+------------------------------------------------------------------------------------------------------------------------+
| Note | 1831 | Duplicate index 'a_2' defined on the table 'test.test'. This is deprecated and will be disallowed in a future release. |
+-------+------+------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

------------------------

a. I didn't observed the said error. Bug TCs probably is missing the initial steps or setting tried or things/behavior has changed since the bug was logged.

----------------------------------------------------------------------------------------------------------------------------------

Said that, RSU is special mode provided to facilitate execution of major DDL workload.
There is set process to execute such workload under RSU. (here is good example about it
http://severalnines.com/blog/online-schema-upgrade-mysql-galera-cluster-using-rsu-method)
If that is followed we can expect the proper behavior.
Anything beside it can cause undefined behavior which I don't foresee to be a bug.
(Of-course it shouldn't crash the cluster).

If we expect some difference in behavior then may be logging a FEATURE REQUEST would help but at-least for the cases like these I don't foresee why is that needed.