hadoop ha切换时候会报个异常，并且client会一直连原来active的那个namenode？？

1：HA 切换的时候报这个是正常的么？？
2015-02-02 18:12:56,091 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Stopping services started for standby state
2015-02-02 18:12:56,091 WARN org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Edit log tailer interrupted
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.doWork(EditLogTailer.java:334)
at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.access$200(EditLogTailer.java:279)
at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread$1.run(EditLogTailer.java:296)
at org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:456)
at org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.run(EditLogTailer.java:292)
2015-02-02 18:12:56,193 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services required for active state
2015-02-02 18:12:56,197 INFO org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager: Starting recovery process for unclosed journal segments...
2015-02-02 18:12:56,283 INFO org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager: Successfully started new epoch 5
2015-02-02 18:12:56,283 INFO org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager: Beginning recovery of unclosed segment starting at txid 29642
2015-02-02 18:12:56,334 INFO org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager: Recovery prepare phase complete. Responses:
10.21.126.38:8485: segmentState { startTxId: 29642 endTxId: 29642 isInProgress: true } lastWriterEpoch: 4 lastCommittedTxId: 29641
2015-02-02 18:12:56,335 INFO org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager: Using longest log: 10.21.126.38:8485=segmentState {
  startTxId: 29642
  endTxId: 29642
  isInProgress: true
}
lastWriterEpoch: 4
lastCommittedTxId: 29641

2015-02-02 18:12:56,415 INFO org.apache.hadoop.hdfs.server.namenode.FileJournalManager: Recovering unfinalized segments in /mnt/disk0/test-hadoop/data/namenode/current

2：HA切换后client还是会去连接原来active的那个namenode么?
在原来的日志里看到有这个：
2015-02-02 18:25:36,228 ERROR org.apache.hadoop.security.UserGroupInformation: PriviledgedActionException as:test-hadoop (auth:SIMPLE) cause:org.apache.hadoop.ipc.StandbyException: Operation category READ is not supported in state standby2015-02-02 18:25:36,228 INFO org.apache.hadoop.ipc.Server: IPC Server handler 81 on 8020, call org.apache.hadoop.hdfs.protocol.ClientProtocol.getListing from 10.21.126.34:53324 Call#18 Retry#0: error: org.apache.hadoop.ipc.StandbyException: Operation category READ is not supported in state standby