You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/mainnet/net/installation/downloads.rst
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -242,9 +242,9 @@ For the system requirements to run a node, see :ref:`System requirements to run
242
242
243
243
.. dropdown:: Ubuntu |testnet-node-version|
244
244
245
-
To run a node on a server with Ubuntu, `download a Testnet Debian package <https://distribution.testnet.concordium.com/deb/concordium-testnet-node_6.2.3-0_amd64.deb>`_.
245
+
To run a node on a server with Ubuntu, `download a Testnet Debian package <https://distribution.testnet.concordium.com/deb/concordium-testnet-node_6.3.0-0_amd64.deb>`_.
246
246
247
-
- SHA256 checksum of the download: ``5e97f77f3dedfd8921045a3ed4623600281b5331d37e527424a2f01068e6b2b1``
247
+
- SHA256 checksum of the download: ``92e08a403c78014727be8fb91b305beac403d510e360ea7a73550d8875af068e``
248
248
249
249
To learn how to run a node with Ubuntu, see :ref:`Run a node on a server with Ubuntu <run-node-ubuntu>`.
250
250
@@ -258,13 +258,13 @@ For the system requirements to run a node, see :ref:`System requirements to run
258
258
259
259
.. dropdown:: Windows |testnet-node-version|
260
260
261
-
To run a node on Windows, `download a Testnet Windows Installer package <https://distribution.concordium.software/windows/Signed/Node-6.2.3-0.msi>`_. **Please be aware that you should backup your configuration, as the installer will overwrite the current configuration with a standard configuration.**
261
+
To run a node on Windows, `download a Testnet Windows Installer package <https://distribution.concordium.software/windows/Signed/Node-6.3.0-0.msi>`_. **Please be aware that you should backup your configuration, as the installer will overwrite the current configuration with a standard configuration.**
262
262
263
263
To learn how to run a node on Windows, see :ref:`Run and manage a node on Windows <run-node-windows>`.
264
264
265
265
.. dropdown:: Mac |testnet-node-version|
266
266
267
-
To run a node on macOS, `download a Testnet macOS installer package <https://distribution.concordium.software/macos/signed/concordium-node-6.2.3-0.pkg>`_.
267
+
To run a node on macOS, `download a Testnet macOS installer package <https://distribution.concordium.software/macos/signed/concordium-node-6.3.0.pkg>`_.
268
268
269
269
To learn how to run a node on Mac, see :ref:`Run and manage a node on macOS <run-node-macos>`.
Copy file name to clipboardExpand all lines: source/mainnet/net/installation/previous-node-downloads.rst
+14Lines changed: 14 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ Windows - Mainnet and Testnet
14
14
15
15
**Please be aware that you should backup your configuration, as the installer will overwrite the current configuration with a standard configuration.**
Copy file name to clipboardExpand all lines: source/mainnet/net/release-notes/release-notes-lp.rst
+15-6Lines changed: 15 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1038,17 +1038,26 @@ Mainnet
1038
1038
Testnet
1039
1039
-------
1040
1040
1041
-
November 28, 2023
1041
+
February 20, 2024
1042
1042
1043
-
Version 6.2.3 removes the V1 gRPC API. This removes the configuration options ``CONCORDIUM_NODE_RPC_SERVER_PORT``, ``CONCORDIUM_NODE_RPC_SERVER_ADDRESS``, ``CONCORDIUM_NODE_RPC_SERVER_TOKEN``, ``CONCORDIUM_NODE_DISABLE_RPC_SERVER_NODE_ENDPOINTS`` and their command line equivalents. An additional health-check service was also added to the V2 GRPC API. This service conforms to the `standard GRPC health service API <https://github.com/grpc/grpc-proto/blob/master/grpc/health/v1/health.proto>`__.
1043
+
The 6.3.0 release contains the following fixes and improvements:
1044
1044
1045
-
As part of the tokenomics changes the node has new configuration options that use the new terminology. The existing options using the legacy terminology are still supported, however they are hidden.
1045
+
- Fixed a bug where ``GetBlockPendingUpdates`` fails to report pending updates to the finalization committee parameters.
1046
+
- GRPC queries are now run in dedicated threads. This improves node resource management and increases responsiveness of the GRPC server in cases of high number of concurrent queries. To support this a new option ``--grpc2-max-threads`` (environment variable ``CONCORDIUM_NODE_GRPC2_MAX_THREADS``) has been added, which specifies the number of threads that the node should use for processing gRPC requests. If not set this defaults to the number of (logical) CPUs.
1047
+
- The option ``--grpc2-max-concurrent-streams`` now defaults to 200 from the previous unbounded value. This makes the node defaults safer.
1048
+
- Startup time of the node has improved on all supported distributions.
1046
1049
1047
-
A ``DryRun`` endpoint has also been that allows simulating the execution of transactions.
1050
+
.. dropdown:: Previous releases
1048
1051
1049
-
The account map is now kept solely on disk in a separate LMDB database and it is no longer part of the internal block state database. This change results in significantly reduced resource usage for the node.
1052
+
.. dropdown:: 6.2.3 - November 28, 2023
1050
1053
1051
-
.. dropdown:: Previous releases
1054
+
Version 6.2.3 removes the V1 gRPC API. This removes the configuration options ``CONCORDIUM_NODE_RPC_SERVER_PORT``, ``CONCORDIUM_NODE_RPC_SERVER_ADDRESS``, ``CONCORDIUM_NODE_RPC_SERVER_TOKEN``, ``CONCORDIUM_NODE_DISABLE_RPC_SERVER_NODE_ENDPOINTS`` and their command line equivalents. An additional health-check service was also added to the V2 GRPC API. This service conforms to the `standard GRPC health service API <https://github.com/grpc/grpc-proto/blob/master/grpc/health/v1/health.proto>`__.
1055
+
1056
+
As part of the tokenomics changes the node has new configuration options that use the new terminology. The existing options using the legacy terminology are still supported, however they are hidden.
1057
+
1058
+
A ``DryRun`` endpoint has also been that allows simulating the execution of transactions.
1059
+
1060
+
The account map is now kept solely on disk in a separate LMDB database and it is no longer part of the internal block state database. This change results in significantly reduced resource usage for the node.
0 commit comments