Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

[PIE-1710] Expose a CLI option to configure the life time of transaction messages. #1610

Conversation

AbdelStark
Copy link
Contributor

@AbdelStark AbdelStark commented Jun 26, 2019

PR description

We want to make configurable the life time of transactions. This life time is used to drop incoming transactions from the network if they are too old.

  • TX_KEEP_ALIVE is not anymore a constant and is set in the constructor of TransactionsMessageHandler
  • the TransactionPoolFactory pass the option to the TransactionsMessageHandler
  • add a cli option --tx-pool-keep-alive-seconds

Fixed Issue(s)

#PIE-1710

…ion messages.

- add a cli option `--tx-pool-message-keep-alive-seconds`
@AbdelStark AbdelStark added enhancement New feature or request api Related to public APIs labels Jun 26, 2019
@AbdelStark AbdelStark merged commit f06c2c1 into PegaSysEng:master Jun 26, 2019
@AbdelStark AbdelStark deleted the feature/pie-1710-cli-opt-tx-msg-timeout branch June 26, 2019 15:36
paramLabel = MANDATORY_INTEGER_FORMAT_HELP,
description = "Keep alive of transactions in seconds (default: ${DEFAULT-VALUE})",
arity = "1")
private final Integer txMessageKeepAliveSeconds = TransactionPool.DEFAULT_TX_MSG_KEEP_ALIVE;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this should be a visible option - it's potentially very misleading for users and ideally wouldn't ever kick in since we should keep up with transaction messages. I'd say it should just be a -X option.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api Related to public APIs enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants