# Migration make the aerospike can't writing
**URL:** https://discuss.aerospike.com/t/migration-make-the-aerospike-cant-writing/3566
**Category:** Migration
**Created:** [November 1, 2016, 1:07am UTC](https://discuss.aerospike.com/t/migration-make-the-aerospike-cant-writing/3566 "2016-11-01T01:07:54Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@jessica](https://discuss.aerospike.com/u/jessica)
#### Post date: [November 1, 2016, 1:07am UTC](https://discuss.aerospike.com/t/migration-make-the-aerospike-cant-writing/3566/1 "2016-11-01T01:07:54Z")
I have about 1 billion data, saved in the 3 nodes. Each node has 16 core cpu and 64G mem. A service writes the data with a lot of concurrency. But after the migration began, the service could not write to aerospike. Connections were always timeout. The migration looked normal. But the service can not work. I think it will be restore normal after migration. But I can not accept the service to stop working.
---
### Author:  [@jessica](https://discuss.aerospike.com/u/jessica)
#### Post date: [November 1, 2016, 3:40am UTC](https://discuss.aerospike.com/t/migration-make-the-aerospike-cant-writing/3566/2 "2016-11-01T03:40:31Z")
I set an parameter and now it works.
asadm -e “asinfo -v ‘set-config:context=service;write-duplicate-resolution-disable=true’”