I would like to know what will happen to missing transactions as revealed by the curl command.
My node (IRI version 1.4.1.4 in sync) now has about 10 and sort of slowing creeping up by the hour.
curl http://localhost:14265 -X POST -H 'Content-Type: application/json'
-H 'X-IOTA-API-Version: 1.4' -d '{"command": "getMissingTransactions"}' | jq
IRI keeps track of txs which are missing. The node will fetch the hash of one of its missing txs and ask a neighbor whether he has it. If the neighbor has it, it will remove the tx from its missing list after receiving it. If the neighbor doesn't have it, the node will give it another try when the tx gets selected again (could be a different neighbor this time).
However since the tx might be really non-existent (e.g. a tx specified a bogus trunk and/or branch), IRI has built in something that when selecting a missing tx, it already removes the tx from the missing list with a small probability (like 1%). This way the missing tx-list is regularly purged from bad/non-existent txs. A restart clears the complete missing list of course.
