disaster recovery scenarios for solr cloud and zookeeper

Hi, Solr 4.x is architected with a dependency on Zookeeper, and Zookeeper is expected to have a very high (perfect?) availability. With 3 or 5 zookeeper nodes, it is possible to manage zookeeper maintenance and online availability to be close to %100. But what is the worst case for Solr if for som

Solr URL uses non-standard format with pound sign

RFC1738. Here is the error message: # Is there another way to access the Solr URL without using the "#" sign? Thanks, Dennis Haller