XDCR never starts up after deletion and recreation of bucket (with the same name) in a unidirectional scenario

• Create a unidirectional XDCR on a bucket from one cluster to another.
• On the source, delete the bucket and recreate one other with the same name.
• On the XDCR tab in the UI, the status of the ongoing replication says "Starting up" but never actually starts replicating.

A whole bunch of these seen on the source node:

[xdcr:error,2012-11-26T16:15:43.020,ns_1@10.3.3.150:<0.8215.1>:xdc_vbucket_rep:terminate:284]Shutting xdcr vb replicator ({init_state,
{rep,
<<"7554df57af6a5ac799f90c77413e5c88/default/default">>,
<<"default">>,
<<"/remoteClusters/7554df57af6a5ac799f90c77413e5c88/buckets/default">>,
[

{connection_timeout,180000},
{continuous,true},
{http_connections,20},
{retries,2},
{socket_options,
[{keepalive,true},{nodelay,false}]},
{worker_batch_size,500},
{worker_processes,4}]},
187,<0.4677.0>,<0.4678.0>,<0.4674.0>}) down without ever successfully initializing: {db_not_found, <<"default/187">>}
[xdcr:error,2012-11-26T16:15:43.074,ns_1@10.3.3.150:<0.6622.1>:xdc_vbucket_rep:handle_info:83]Error initializing vb replicator ({init_state,
{rep,
<<"7554df57af6a5ac799f90c77413e5c88/default/default">>,
<<"default">>,
<<"/remoteClusters/7554df57af6a5ac799f90c77413e5c88/buckets/default">>,
[{connection_timeout,180000}

,

{continuous,true}

,

{http_connections,20}

,

{retries,2}

,
{socket_options,
[

{keepalive,true}

,

{nodelay,false}

]},

{worker_batch_size,500}

,

{worker_processes,4}

]},
176,<0.4677.0>,<0.4678.0>,<0.4674.0>}):{throw,
{db_not_found,
<<"default/176">>}}

If replication is recreated however, replication starts up just fine.
Solutions:

• Bucket deletion either not to be allowed with an ongoing replication
• Upon bucket recreation with the same name, replication to be automatically recreated too.