MySql database replication problem with error no: 1594

We have maintained one MySQL master server and two slave MySQL server. One of the MySQL slave server was down for more than a week. I tried to re-import all the database and restart the slave. But got the error 1594:

MySql Version (Master): mysql  Ver 14.14 Distrib 5.7.13
MySql Version (Slave): mysql  Ver 14.14 Distrib 5.7.13
Replication method: GTID based

Steps followed to re-import the DB and start the slave:

mysql>stop slave;  
mysql>reset master;  
shell>mysql -u root -p < masterdbdump.sql
mysql> start slave;

Slave status after this:

mysql> show slave statusG
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: *.*.*.*
                  Master_User: abcd
                  Master_Port: 3306
                Coect_Retry: 60
              Master_Log_File: mysql-bin.000189
          Read_Master_Log_Pos: 4945
               Relay_Log_File: relay-log-slave.000128
                Relay_Log_Pos: 17850491
        Relay_Master_Log_File: mysql-bin.000166
             Slave_IO_Ruing: Yes
            Slave_SQL_Ruing: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 1594
                   Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by ruing 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by ruing 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 17850278
              Relay_Log_Space: 1363536799
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 1594
               Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by ruing 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by ruing 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 111
                  Master_UUID: e9c6aa57-fefd-11e5-a9a4-002590478768
             Master_Info_File: /opt/db/mysql/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Ruing_State: 
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 160902 12:30:56
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: e9c6aa57-fefd-11e5-a9a4-002590478768:5296716-14354558
            Executed_Gtid_Set: e9c6aa57-fefd-11e5-a9a4-002590478768:1-14354551
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Chael_Name: 
           Master_TLS_Version: 
1 row in set (0.01 sec)

from the mysql error log:

2016-09-02T06:45:56.605819Z 1 [ERROR] Error in Log_event::read_log_event(): 'Event too small', data_len: 0, event_type: 0
2016-09-02T06:45:56.605852Z 1 [ERROR] Error reading relay log event for chael '': slave SQL thread aborted because of I/O error
2016-09-02T06:45:56.605879Z 1 [ERROR] Slave SQL for chael '': Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by ruing 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by ruing 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 1594
2016-09-02T06:45:56.605886Z 1 [ERROR] Error ruing query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000166' position 17850278
2

Any suggestion on this issue would be appreciable.