Vineyardd will crashed when reset the etcd client

[dashanji]

Describe your problem

In instanceUpdate, we will reset the etcd client. At the same time, the other thread have started a lock pplx task with the previous etcd client. Then, the vineyardd will crash with the following log.

││   __cxxabiv1::__terminate(void (*)()) + 0x6                                                        ││   std::terminate() + 0x11                                                                          ││   pplx::details::_ExceptionHolder::~_ExceptionHolder() + 0x18                                      ││   std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count() + 0x38                        ││   std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count() + 0x38                        │
│   vineyard::EtcdMetaService::UpdateEndpoint() + 0xD22                                              │
│   pplx::details::_TaskProcHandle::_RunChoreBridge(void*) + 0x1F                                    │
│   boost::asio::detail::completion_handler<boost::_bi::bind_t<void, void (*)(void*), boost::_bi::li │
│   boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::sco │
│   boost::asio::detail::scheduler::run(boost::system::error_code&) + 0xD5                           │
│   crossplat::threadpool::initialize_with_threads(unsigned long) + 0x132                            │
│   boost_asio_detail_posix_thread_function + 0x17                                                   │
│   pthread_condattr_setpshared + 0x4D4                                                              │
│   __xmknodat + 0x23C

[github-actions]

/cc @dashanji, this issus/pr has had no activity for for a long time, could you folks help to review the status ?
To suppress further notifications,

• for issues,
  • if it is waiting for further response from the reporter/author, please help to add the label requires-further-info,
  • if you have already started working on it, please add the label work-in-progress to the issue,
  • if this issue requires further designing discussion and not in current plan, or won't be fixed, please add the label requires-further-discussion or wontfix to the issue,
• for pull requests,
  • if you are still working on it and it is not ready for reviewing, please convert this pull request as draft PR,
  • if you have decided to hold this development on, please add the requires-further-discussion label to the pull request.
    Thanks!

[github-actions]

/cc @dashanji, this issus/pr has had no activity for for a long time, could you folks help to review the status ?
To suppress further notifications,

• for issues,
  • if it is waiting for further response from the reporter/author, please help to add the label requires-further-info,
  • if you have already started working on it, please add the label work-in-progress to the issue,
  • if this issue requires further designing discussion and not in current plan, or won't be fixed, please add the label requires-further-discussion or wontfix to the issue,
• for pull requests,
  • if you are still working on it and it is not ready for reviewing, please convert this pull request as draft PR,
  • if you have decided to hold this development on, please add the requires-further-discussion label to the pull request.
    Thanks!