1

What happens to the transactions submitted to light node in the following scenarios?
1) Light node does not have a network connection with its peers.I could find that the transactions are submitted successfully to light node but not broadcasted to its peers.
2) Light node is stopped before it can broadcast the transaction submitted.

I could find transactions.rlp file in geth folder for "FULL" nodes. Is this file related to pending transactions somehow? If so, why there is no such file for light client geth and how the transaction queue works for light client? Is it stored internally which is reset on every restarts for a light client?

0

1) Light node does not have a network connection with its peers.I could find that the transactions are submitted successfully to light node but not broadcasted to its peers.

I found that by default the Maximum peer count for LES is ZERO then it might be the problem. Can you try to increase LES 1 or 2 peer(s) to see what's happen.

  • I am using --lightserv 70 on the full node and its enodeId is added to light client's static nodes file. When the nodes were started, the light client got synced successfully and the transactions were getting submitted and broadcasted. The issue of 'not broadcasting transactions' with the light client started after a restart of light node. But then it was importing new blocks successfully. On further restarts, it is observed that those transactions which are not broadcasted earlier is not existing on the light client node as well.(eth.getTransaction() is returning null). – Jith Aug 21 '18 at 4:36
  • okay, understand your problem now. I think that it'd better to edit your question then everyone can understand it more clearly ;) – Ha ĐANG Aug 21 '18 at 4:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.