# Urgent: Migration stuck v3.8.1, missing acks from node

**URL:** <https://discuss.aerospike.com/t/urgent-migration-stuck-v3-8-1-missing-acks-from-node/4289>\
**Category:** General Discussion\
**Tags:** migration\
**Created:** [June 20, 2017, 2:26pm UTC](https://discuss.aerospike.com/t/urgent-migration-stuck-v3-8-1-missing-acks-from-node/4289 "2017-06-20T14:26:47Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![kporter](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/kporter/32/515_2.png) [@kporter](https://discuss.aerospike.com/u/kporter)\
**Post date:** [June 28, 2017, 6:05pm UTC](https://discuss.aerospike.com/t/urgent-migration-stuck-v3-8-1-missing-acks-from-node/4289/21 "2017-06-28T18:05:29Z")

</div>

Well, doesn’t seem very interesting after all. There is a little thrash from your clients but doesn’t seem to terrible (do you guys periodically restart groups of clients?). But hb and fabric sockets are fairly stable and show signs of a node being ejected and re-added. I don’t see any strong evidence here of a network issue.

In later releases there were improvements to fabric and hb layers (also clustering in 3.3.13). The fabric on your server is showing a concerning message that I haven’t seen logged before:

> Jun 22 2017 23:14:18 GMT: INFO (fabric): (fabric.c:1288) can’t write to notification file descriptor: will probably have to take down process

I believe this was a code path that wasn’t expected to be reachable. The newer servers definitely will not have this issue since this particular socket was eliminated.

[Previous page](https://discuss.aerospike.com/t/urgent-migration-stuck-v3-8-1-missing-acks-from-node/4289.md?page=1)