zero values in ndb_binlog_index

[Odis Yuck]

Hello. I try to set up replication between two clusters.
If I understand correctly, according to this config, mysql must write events in ndb_binlog_index even without working slave:

server-id=3
log-bin-trust-function-creators = 1
log-bin=log-bin.log
binlog-format=ROW
ndb-log-transaction-id=1
ndb-log-update-as-write=0
ndb-log-apply-status=1
replicate-wild-do-table=my_test.replication%
replicate-wild-do-table=mysql.ndb_apply_status
replicate-wild-do-table=mysql.ndb_replication

So, it writes, but in very strange way:

mysql-office> select file,orig_server_id,orig_epoch,position,next_position from mysql.ndb_binlog_index;
+------------------+----------------+------------+----------+---------------+
| file | orig_server_id | orig_epoch | position | next_position |
+------------------+----------------+------------+----------+---------------+
| ./log-bin.000001 | 0 | 0 | 217 | 596 |
+------------------+----------------+------------+----------+---------------+
1 row in set (0,00 sec)

mysql-office> show binlog events;
+----------------+-----+-------------+-----------+-------------+-------------------------------------------------------------+
| Log_name | Pos | Event_type | Server_id | End_log_pos | Info |
+----------------+-----+-------------+-----------+-------------+-------------------------------------------------------------+
| log-bin.000001 | 4 | Format_desc | 3 | 120 | Server ver: 5.6.23-ndb-7.4.5-cluster-gpl-log, Binlog ver: 4 |
| log-bin.000001 | 120 | Query | 3 | 217 | use `my_test`; truncate table replication |
| log-bin.000001 | 217 | Query | 3 | 285 | BEGIN |
| log-bin.000001 | 285 | Table_map | 3 | 343 | table_id: 79 (my_test.replication) |
| log-bin.000001 | 343 | Table_map | 3 | 409 | table_id: 71 (mysql.ndb_apply_status) |
| log-bin.000001 | 409 | Write_rows | 3 | 474 | table_id: 71 |
| log-bin.000001 | 474 | Write_rows | 3 | 527 | table_id: 79 flags: STMT_END_F |
| log-bin.000001 | 527 | Query | 3 | 596 | COMMIT |
+----------------+-----+-------------+-----------+-------------+-------------------------------------------------------------+
8 rows in set (0,00 sec)

There are simple situation (no working slave), but when replication is and working, all fine (data changes in both clusters, there is some non zero values in ndb_apply_status) except ndb_binlog_index.

Is it bug or my fault in configuration?