The mongos has the following assertion message in the log, when an auto split occurs on a high top chunk and maxSize prevents the move chunk:
m30999| 2014-10-27T16:43:22.123-0400 I SHARDING [conn1] autosplitted test.topchunk shard: ns: test.topchunk, sh ard: shard0000:localhost:30000, lastmod: 1|38||000000000000000000000000, min: { x: 1475.0 }, max: { x: MaxKey } into 3 (splitThreshold 943718) (migrate suggested) m30999| 2014-10-27T16:43:22.124-0400 D SHARDING [conn1] found 2 shards listed on config server(s): localhost:30 000 (127.0.0.1) m30999| 2014-10-27T16:43:22.125-0400 D SHARDING [conn1] shard0000 has already reached the maximum total chunk s ize. m30999| 2014-10-27T16:43:22.125-0400 D SHARDING [conn1] shard0001 has already reached the maximum total chunk s ize. m30999| 2014-10-27T16:43:22.125-0400 I SHARDING [conn1] moving chunk (auto): ns: test.topchunk, shard: shard000 0:localhost:30000, lastmod: 2|4||000000000000000000000000, min: { x: 2749.0 }, max: { x: MaxKey } to: m30999| 2014-10-27T16:43:22.125-0400 D - [conn1] User Assertion: 9:Empty host component parsing HostAndPort from "" m30999| 2014-10-27T16:43:22.125-0400 W SHARDING [conn1] could not autosplit collection test.topchunk :: caused by :: 9 Empty host component parsing HostAndPort from ""