replicate_events_marked_for_skip didn't work on Galera cluster

the cluster & replication :

https://farm8.staticflickr.com/7544/15874745401_d3975432f6_b.jpg

my galera.ini

[mysqld]
#mysql settings

log-slave-updates=1
default-storage-engine=innodb
query_cache_size=0
query_cache_type=0
bind-address=0.0.0.0

server-id=1746717299

skip-slave-start

datadir = /data/mysql/data
#galera settings
wsrep_provider=/usr/lib/galera/libgalera_smm.so
wsrep_cluster_name="iways_cluster"
wsrep_cluster_address="gcomm://10.7.20.3,10.7.20.4,10.7.20.6"
wsrep_sst_method=rsync
wsrep_provider_options="gcache.size=20G"

#innoDB
innodb_file_per_table
connect_timeout = 60
wait_timeout = 3600
innodb_buffer_pool_size = 16G
innodb_flush_method = O_DIRECT

innodb_log_file_size = 64M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_autoinc_lock_mode=2

#for master

binlog_format=ROW
log_bin = /data/mysql/binlog/mariadb-bin
log_bin_index = /data/mysql/binlog/mariadb-bin.index
max_binlog_size = 1G
expire_logs_days = 10

sync_binlog=1

sort_buffer_size = 10M
bulk_insert_buffer_size = 16M
tmp_table_size = 64M
max_heap_table_size = 64M

#log
slow_query_log_file = /data/mysql/log/mariadb-slow.log
long_query_time = 1

performance_schema = 'ON'

collation-server = utf8_unicode_ci
character-set-server = utf8
init-connect = 'SET NAMES utf8'

max_connections = 500
open_files_limit = 65535
log-error=/data/mysql/log/error.log

on node 1 :
use PRODUCTION;
CREATE TABLE `test` (
`id` int(11) NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

INSERT INTO `PRODUCTION`.`test` (`id`) VALUES ('1'), ('2');

====
two rows are present on all servers (and on slave)

slave have configuration :
replicate-events-marked-for-skip = filter_on_slave

=========
if i run on node 2 :
SET @@skip_replication = ON;
delete from test where id =1;

it's work perfectly, i still got the line on slave

========

if i run on node 1 or 3 :
SET @@skip_replication = ON;
delete from test where id =1;

it's didn't work, I lost the line on the slave.

-I saw this problem has been fixed on 10.0.14, I would to know if it was knowed.-