Block gas limit #700
Assignees
Labels
Comments
|
@Magicking |
|
@wenhuancai you can increase the default low gas limit by setting these flags as suggested by @Magicking --miner.gastarget XXX and --miner.gaslimit XXX. |
|
i don't know how to set --miner.gastarget XXX and --miner.gaslimit XXX. |
|
The "exceeds block gas limit" suggests that you are submitting a transaction with gas which exceeds the block gas limit. You need to either increase This parameters suggested earlier should be added to the command line, e.g.: |
|
root@2880e441b23a:/home/anzheng# cat runscript.sh |
|
What is the gasLimit in your genesis? |
|
|
|
|
|
@wenhuancai did you solve the issue? |
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Nov 28, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Nov 28, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Nov 28, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Nov 28, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Nov 28, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 2, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 3, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 3, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 4, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 5, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 5, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 11, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 11, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Dec 21, 2019
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Feb 11, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Feb 19, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Feb 21, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Feb 22, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Mar 1, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Mar 2, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Mar 17, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Mar 17, 2020
Instead of hardcoding guesses regarding what the CI environment will produce as a gas price for the contract deployment be pro-active, ask for a quote and then offer to spend the quote + a million gas to be on the safe side. This should guarantee that there will be enough gas unless there's a bug in the underlying network (which has happened in the past, quorum had a gas bug where it was asking for more than the maximum possible gas). Also downgraded quorum to v2.2.5 because that is considered stabl while 2.3.0 is a beta release and therefore it is possible that has issues with the gas estimates like previous versions did. Changed the gas upper and lower bounds for blocks through the newly introduced CLI flags of Quorum eth: Consensys/quorum#700 (comment) https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L333 https://github.com/jpmorganchase/quorum/blob/v2.2.5/cmd/utils/flags.go#L343 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like the
2.2.2patch imported this commit e8f229b, that changes the default target gas limit to8,000,000(ATOW: public ethereum mainnet) instead of the previous higher defined gas limit.You now need with the
2.2.2+version to use--miner.gastarget XXXand--miner.gaslimit XXXto set an othergasLimitper block.Is this an intended behavior?
An update from
2.2.1to2.2.2has the effect without setting this flag to reduce thegasLimitper block to the limit above.The text was updated successfully, but these errors were encountered: