Pool member request with checkstatus=1 is not locking data

/api/v3/pool/deploy//member/status/?checkstatus=1 is not locking the data in networkapi.
As such, it can cause concurrence problems with another requests that change pool member table.

Made two request, to delete member and to check status and it inserted a status of a non existent member after removing it.