pd add a peer and them remove it quickly #343
Description
This is for tikv/tikv#1174
2016-10-15 00:40:17,110 raft.rs:642 - INFO - [region 12314] 12317 became leader at term 7
2016-10-15 07:00:37,858 pd.rs:161 - INFO - [region 12314] try to change peer AddNode id: 18769 store_id: 1 for region id: 12314 start_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\206\314\317\000\000\000\000\000\372" end_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\207\216\371\000\000\000\000\000\372" region_epoch {conf_ver: 7 version: 919} peers {id: 12315 store_id: 5} peers {id: 12316 store_id: 6} peers {id: 12317 store_id: 4}
2016-10-15 peer.rs:691 - INFO - [region 12314] 12317 propose conf change AddNode peer 18769
2016-10-15 07:00:37,859 peer.rs:1100 - INFO - [region 12314] 12317 execute admin command cmd_type: ChangePeer change_peer {change_type: AddNode peer {id: 18769 store_id: 1}}
2016-10-15 07:00:37,859 peer.rs:1126 - WARN - [region 12314] 12317 exec ConfChange "AddNode", epoch: conf_ver: 7 version: 919
2016-10-15 07:00:37,859 peer.rs:1159 - WARN - [region 12314] 12317 add peer id: 18769 store_id: 1 to region id: 12314 start_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\206\314\317\000\000\000\000\000\372" end_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\207\216\371\000\000\000\000\000\372" region_epoch {conf_ver: 7 version: 919} peers {id: 12315 store_id: 5} peers {id: 12316 store_id: 6} peers {id: 12317 store_id: 4}
2016-10-15 07:00:37,859 store.rs:847 - INFO - [region 12314] 12317 notify pd with change peer region id: 12314 start_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\206\314\317\000\000\000\000\000\372" end_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\207\216\371\000\000\000\000\000\372" region_epoch {conf_ver: 8 version: 919} peers {id: 12315 store_id: 5} peers {id: 12316 store_id: 6} peers {id: 12317 store_id: 4} peers {id: 18769 store_id: 1}
2016-10-15 07:00:37,984 pd.rs:161 - INFO - [region 12314] try to change peer RemoveNode id: 18769 store_id: 1 for region id: 12314 start_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\206\314\317\000\000\000\000\000\372" end_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\207\216\371\000\000\000\000\000\372" region_epoch {conf_ver: 8 version: 919} peers {id: 12315 store_id: 5} peers {id: 12316 store_id: 6} peers {id: 12317 store_id: 4} peers {id: 18769 store_id: 1}
2016-10-15 07:00:37,984 peer.rs:691 - INFO - [region 12314] 12317 propose conf change RemoveNode peer 18769
2016-10-15 07:00:37,984 peer.rs:1100 - INFO - [region 12314] 12317 execute admin command cmd_type: ChangePeer change_peer {change_type: RemoveNode peer {id: 18769 store_id: 1}}
2016-10-15 07:00:37,984 peer.rs:1126 - WARN - [region 12314] 12317 exec ConfChange "RemoveNode", epoch: conf_ver: 8 version: 919
2016-10-15 07:00:37,984 peer.rs:1188 - WARN - [region 12314] 12317 remove 18769 from region:id: 12314 start_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\206\314\317\000\000\000\000\000\372" end_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\207\216\371\000\000\000\000\000\372" region_epoch {conf_ver: 8 version: 919} peers {id: 12315 store_id: 5} peers {id: 12316 store_id: 6} peers {id: 12317 store_id: 4} peers {id: 18769 store_id: 1}
2016-10-15 07:00:37,984 store.rs:847 - INFO - [region 12314] 12317 notify pd with change peer region id: 12314 start_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\206\314\317\000\000\000\000\000\372" end_key: "t\200\000\000\000\000\000\000\377X_r\200\000\000\000\002\377\207\216\371\000\000\000\000\000\372" region_epoch {conf_ver: 9 version: 919} peers {id: 12315 store_id: 5} peers {id: 12316 store_id: 6} peers {id: 12317 store_id: 4}
As we can see, PD adds the peer 18769 at 07:00:37,859, but removes it at 07:00:37,984, the balance strategy seems not working well.