importprivkey fails when walletnotify is set #6084

If I have walletnotify set in my conf and try to import a private key, it always fails with:

$ bitcoin-cli importprivkey $key
error: {"code":-1,"message":"boost::thread_resource_error: Resource temporarily unavailable"}

I was watching the debug log when this happens, and see the rescan is calling AddToWallet for ALL past transactions, not just for the new imported private key. And it's trying to run the walletnotify program for every transaction.

The only way I can get this to work is to first stop bitcoin, disable walletnotify, then restart bitcoin to perform the importprivkey, then stop and re-enable walletnotify and restart.

What are you running exactly with walletnotify?

See also #6095 which is the same complaint for importaddress. Unclear if this is a bug though ...

What are you running exactly with walletnotify?

A bash script that calls gettransaction and getbalance.

See also #6095 which is the same complaint for importaddress. Unclear if this is a bug though ...

Yes, same problem. And I agree with the reporter of that ticket- it's a bug if it's resulting in wallnetnotify script to be called for every transaction in the wallet, and not just the transactions belonging to the new key/address.

Even if this bug and #6095 are resolved to only trigger notifications corresponding only to the specified key/address, running bitcoind -rescan will result in too many simultaneous processes. A thread pool would solve that, right?

The guy in #6095 didn't listen when I told him his system could still fail under normal operation even if the rescan behavior were made specific during an import. He furthermore could have skipped the rescan entirely if he used rescan=false as he indicated the key was new.

#6031 also a duplicate.

I assume this is no longer an issue in the same way as https://github.com/bitcoin/bitcoin/issues/6095