We have deployed a replicated sharded cluster with 3 shards, each shard is a 3 member replica set(Primary,Secondary and Arbiter).
Also we are running 3 mongos and 3 config server instances.
We are importing data in this cluster form SQL server using .net service. This service uses MongoDB driver for .net. When we step down one of the primary, arbiter elects new primary and the cluster is up and running, but the MongoDB driver in the service waits for the write concern response from the previous primary, and gets timed out after some time.
Screen shot of the error from .net service is attached.

MongoDB version is 3.0.6 and storage engine is wiredTiger