Skip to content

Commit 42496cf

Browse files
korydraughnalanking
authored andcommitted
[irods/irods#7949] Add note about deprecating parallel transfer over the high ports.
1 parent 11bec8c commit 42496cf

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

docs/system_overview/configuration.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -938,6 +938,9 @@ See [set_grid_configuration](../../icommands/administrator/#set_grid_configurati
938938

939939
## Managing Parallel Transfer Threads
940940

941+
!!! Note
942+
The high ports are deprecated as of iRODS 4.3.4 and will be removed in a later version. Future versions of iRODS will perform parallel transfers using the zone port _(defaults to 1247)_. See [Parallel Transfer](../../system_overview/data_objects/#parallel-transfer) for more information.
943+
941944
When transferring large amounts of data between the client and server or even between servers, the number of threads used to read and write data can be configured by the administrator.
942945

943946
First, we will go over how to configure what "large amounts of data" means. This is a configurable value that is controlled by the `maximum_size_for_single_buffer_in_megabytes` setting in `server_config.json`. This setting controls the maximum size of a particular file or data object that will be put into an in-memory buffer. If the size of the file or data object to read or write exceeds this size, iRODS will initiate what is known as a "parallel transfer".

docs/system_overview/troubleshooting.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -439,6 +439,9 @@ The iRODS Rule Language rule engine variable scoping rules are summarized as:
439439

440440
## Parallel Transfer Port Contention
441441

442+
!!! Note
443+
The high ports are deprecated as of iRODS 4.3.4 and will be removed in a later version. Future versions of iRODS will perform parallel transfers using the zone port _(defaults to 1247)_. See [Parallel Transfer](../../system_overview/data_objects/#parallel-transfer) for more information.
444+
442445
The iRODS Server will issue a LOG_NOTICE when it unsuccessfully attempts to claim an available port while setting up a parallel transfer portal.
443446

444447
```
@@ -710,6 +713,9 @@ This technique should only be used to dig out of this serious situation or for t
710713

711714
## Firewalls dropping long-idle connections during parallel transfer
712715

716+
!!! Note
717+
The high ports are deprecated as of iRODS 4.3.4 and will be removed in a later version. Future versions of iRODS will perform parallel transfers using the zone port _(defaults to 1247)_. See [Parallel Transfer](../../system_overview/data_objects/#parallel-transfer) for more information.
718+
713719
iRODS 4.2 and prior have three different ways to move data: single-buffer, streaming, and parallel transfer. Both single-buffer and streaming transfers are on port 1247 and never have an idle connection. The parallel transfer method connects on port 1247, constructs a portal of high ports, and then moves data over those high ports. Once the transfer is complete, control returns to port 1247 for the connection cleanup and bookkeeping. If the transfer takes long enough, local network firewall timeouts may be tripped and the initial port 1247 connection may be severed.
714720

715721
### iRODS 4.3.1 and later

0 commit comments

Comments
 (0)