141116  0:51:17 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

Server version: 10.0.14-MariaDB-wsrep-log
key_buffer_size=57671680
read_buffer_size=65536
max_used_connections=113
max_threads=501
thread_count=45
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 238333 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f69f568d008
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7f69dabb5c78 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb9158b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x742168]
/lib64/libpthread.so.0(+0xf710)[0x7f6ff28cc710]
/usr/sbin/mysqld(_ZN10Rpl_filterD1Ev+0x70)[0x5632e0]
/usr/sbin/mysqld(_Z15free_rpl_filterPKcP10Rpl_filter+0x19)[0x55a6a9]
/usr/sbin/mysqld(_ZN11NAMED_ILIST14delete_elementEPKcjPFvS1_PhE+0x75)[0x55a7e5]
/usr/sbin/mysqld(_ZN11Master_infoD2Ev+0x2f)[0x69c7df]
/usr/sbin/mysqld(_ZN11Master_infoD0Ev+0x11)[0x69c971]
/usr/sbin/mysqld[0x6eff03]
/usr/sbin/mysqld(_Z24wsrep_replay_transactionP3THD+0x27e)[0x6f0f3e]
/usr/sbin/mysqld[0x5e33d0]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1770)[0x5e4be0]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1ca)[0x5e547a]
/usr/sbin/mysqld(_Z26threadpool_process_requestP3THD+0xa7)[0x6d7fa7]
/usr/sbin/mysqld[0x71775d]
/lib64/libpthread.so.0(+0x79d1)[0x7f6ff28c49d1]
/lib64/libc.so.6(clone+0x6d)[0x7f6ff13f59dd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f69db022020): is an invalid pointer
Connection ID (thread ID): 32
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
141116 00:51:25 mysqld_safe Number of processes running now: 0
141116 00:51:25 mysqld_safe WSREP: not restarting wsrep node automatically
141116 00:51:25 mysqld_safe mysqld from pid file /data/lib/mysql/SESAMMALSQL02.pid ended