perf: websocket grid connectivity for all internode communication (#18461)
This PR adds a WebSocket grid feature that allows servers to communicate via
a single two-way connection.
There are two request types:
* Single requests, which are `[]byte => ([]byte, error)`. This is for efficient small
roundtrips with small payloads.
* Streaming requests which are `[]byte, chan []byte => chan []byte (and error)`,
which allows for different combinations of full two-way streams with an initial payload.
Only a single stream is created between two machines - and there is, as such, no
server/client relation since both sides can initiate and handle requests. Which server
initiates the request is decided deterministically on the server names.
Requests are made through a mux client and server, which handles message
passing, congestion, cancelation, timeouts, etc.
If a connection is lost, all requests are canceled, and the calling server will try
to reconnect. Registered handlers can operate directly on byte
slices or use a higher-level generics abstraction.
There is no versioning of handlers/clients, and incompatible changes should
be handled by adding new handlers.
The request path can be changed to a new one for any protocol changes.
First, all servers create a "Manager." The manager must know its address
as well as all remote addresses. This will manage all connections.
To get a connection to any remote, ask the manager to provide it given
the remote address using.
```
func (m *Manager) Connection(host string) *Connection
```
All serverside handlers must also be registered on the manager. This will
make sure that all incoming requests are served. The number of in-flight
requests and responses must also be given for streaming requests.
The "Connection" returned manages the mux-clients. Requests issued
to the connection will be sent to the remote.
* `func (c *Connection) Request(ctx context.Context, h HandlerID, req []byte) ([]byte, error)`
performs a single request and returns the result. Any deadline provided on the request is
forwarded to the server, and canceling the context will make the function return at once.
* `func (c *Connection) NewStream(ctx context.Context, h HandlerID, payload []byte) (st *Stream, err error)`
will initiate a remote call and send the initial payload.
```Go
// A Stream is a two-way stream.
// All responses *must* be read by the caller.
// If the call is canceled through the context,
//The appropriate error will be returned.
type Stream struct {
// Responses from the remote server.
// Channel will be closed after an error or when the remote closes.
// All responses *must* be read by the caller until either an error is returned or the channel is closed.
// Canceling the context will cause the context cancellation error to be returned.
Responses <-chan Response
// Requests sent to the server.
// If the handler is defined with 0 incoming capacity this will be nil.
// Channel *must* be closed to signal the end of the stream.
// If the request context is canceled, the stream will no longer process requests.
Requests chan<- []byte
}
type Response struct {
Msg []byte
Err error
}
```
There are generic versions of the server/client handlers that allow the use of type
safe implementations for data types that support msgpack marshal/unmarshal.
2023-11-20 20:09:35 -05:00
|
|
|
// Code generated by "stringer -type=HandlerID -output=handlers_string.go -trimprefix=Handler msg.go handlers.go"; DO NOT EDIT.
|
|
|
|
|
|
|
|
|
|
package grid
|
|
|
|
|
|
|
|
|
|
import "strconv"
|
|
|
|
|
|
|
|
|
|
func _() {
|
|
|
|
|
// An "invalid array index" compiler error signifies that the constant values have changed.
|
|
|
|
|
// Re-run the stringer command to generate them again.
|
|
|
|
|
var x [1]struct{}
|
|
|
|
|
_ = x[handlerInvalid-0]
|
|
|
|
|
_ = x[HandlerLockLock-1]
|
|
|
|
|
_ = x[HandlerLockRLock-2]
|
|
|
|
|
_ = x[HandlerLockUnlock-3]
|
|
|
|
|
_ = x[HandlerLockRUnlock-4]
|
|
|
|
|
_ = x[HandlerLockRefresh-5]
|
|
|
|
|
_ = x[HandlerLockForceUnlock-6]
|
|
|
|
|
_ = x[HandlerWalkDir-7]
|
|
|
|
|
_ = x[HandlerStatVol-8]
|
|
|
|
|
_ = x[HandlerDiskInfo-9]
|
|
|
|
|
_ = x[HandlerNSScanner-10]
|
|
|
|
|
_ = x[HandlerReadXL-11]
|
|
|
|
|
_ = x[HandlerReadVersion-12]
|
|
|
|
|
_ = x[HandlerDeleteFile-13]
|
|
|
|
|
_ = x[HandlerDeleteVersion-14]
|
|
|
|
|
_ = x[HandlerUpdateMetadata-15]
|
|
|
|
|
_ = x[HandlerWriteMetadata-16]
|
|
|
|
|
_ = x[HandlerCheckParts-17]
|
2023-11-26 04:32:59 -05:00
|
|
|
_ = x[HandlerRenameData-18]
|
2024-01-25 15:45:46 -05:00
|
|
|
_ = x[HandlerRenameFile-19]
|
|
|
|
|
_ = x[HandlerReadAll-20]
|
|
|
|
|
_ = x[HandlerServerVerify-21]
|
2024-01-30 15:49:02 -05:00
|
|
|
_ = x[HandlerTrace-22]
|
|
|
|
|
_ = x[HandlerListen-23]
|
2024-02-15 19:48:36 -05:00
|
|
|
_ = x[HandlerDeleteBucketMetadata-24]
|
|
|
|
|
_ = x[HandlerLoadBucketMetadata-25]
|
|
|
|
|
_ = x[HandlerReloadSiteReplicationConfig-26]
|
|
|
|
|
_ = x[HandlerReloadPoolMeta-27]
|
|
|
|
|
_ = x[HandlerStopRebalance-28]
|
|
|
|
|
_ = x[HandlerLoadRebalanceMeta-29]
|
|
|
|
|
_ = x[HandlerLoadTransitionTierConfig-30]
|
|
|
|
|
_ = x[HandlerDeletePolicy-31]
|
|
|
|
|
_ = x[HandlerLoadPolicy-32]
|
|
|
|
|
_ = x[HandlerLoadPolicyMapping-33]
|
|
|
|
|
_ = x[HandlerDeleteServiceAccount-34]
|
|
|
|
|
_ = x[HandlerLoadServiceAccount-35]
|
|
|
|
|
_ = x[HandlerDeleteUser-36]
|
|
|
|
|
_ = x[HandlerLoadUser-37]
|
|
|
|
|
_ = x[HandlerLoadGroup-38]
|
|
|
|
|
_ = x[HandlerHealBucket-39]
|
|
|
|
|
_ = x[HandlerMakeBucket-40]
|
|
|
|
|
_ = x[HandlerHeadBucket-41]
|
|
|
|
|
_ = x[HandlerDeleteBucket-42]
|
2024-02-19 17:54:46 -05:00
|
|
|
_ = x[HandlerGetMetrics-43]
|
|
|
|
|
_ = x[HandlerGetResourceMetrics-44]
|
|
|
|
|
_ = x[HandlerGetMemInfo-45]
|
|
|
|
|
_ = x[HandlerGetProcInfo-46]
|
|
|
|
|
_ = x[HandlerGetOSInfo-47]
|
|
|
|
|
_ = x[HandlerGetPartitions-48]
|
|
|
|
|
_ = x[HandlerGetNetInfo-49]
|
|
|
|
|
_ = x[HandlerGetCPUs-50]
|
|
|
|
|
_ = x[HandlerServerInfo-51]
|
|
|
|
|
_ = x[HandlerGetSysConfig-52]
|
|
|
|
|
_ = x[HandlerGetSysServices-53]
|
|
|
|
|
_ = x[HandlerGetSysErrors-54]
|
|
|
|
|
_ = x[HandlerGetAllBucketStats-55]
|
|
|
|
|
_ = x[HandlerGetBucketStats-56]
|
|
|
|
|
_ = x[HandlerGetSRMetrics-57]
|
|
|
|
|
_ = x[HandlerGetPeerMetrics-58]
|
|
|
|
|
_ = x[HandlerGetMetacacheListing-59]
|
|
|
|
|
_ = x[HandlerUpdateMetacacheListing-60]
|
|
|
|
|
_ = x[HandlerGetPeerBucketMetrics-61]
|
|
|
|
|
_ = x[HandlerStorageInfo-62]
|
|
|
|
|
_ = x[HandlerConsoleLog-63]
|
|
|
|
|
_ = x[HandlerListDir-64]
|
|
|
|
|
_ = x[HandlerGetLocks-65]
|
|
|
|
|
_ = x[HandlerBackgroundHealStatus-66]
|
|
|
|
|
_ = x[HandlerGetLastDayTierStats-67]
|
|
|
|
|
_ = x[HandlerSignalService-68]
|
|
|
|
|
_ = x[HandlerGetBandwidth-69]
|
2024-02-28 12:54:52 -05:00
|
|
|
_ = x[HandlerWriteAll-70]
|
2024-03-08 14:08:18 -05:00
|
|
|
_ = x[HandlerListBuckets-71]
|
2024-04-01 19:42:09 -04:00
|
|
|
_ = x[HandlerRenameDataInline-72]
|
2024-04-23 13:15:52 -04:00
|
|
|
_ = x[HandlerRenameData2-73]
|
|
|
|
|
_ = x[handlerTest-74]
|
|
|
|
|
_ = x[handlerTest2-75]
|
|
|
|
|
_ = x[handlerLast-76]
|
perf: websocket grid connectivity for all internode communication (#18461)
This PR adds a WebSocket grid feature that allows servers to communicate via
a single two-way connection.
There are two request types:
* Single requests, which are `[]byte => ([]byte, error)`. This is for efficient small
roundtrips with small payloads.
* Streaming requests which are `[]byte, chan []byte => chan []byte (and error)`,
which allows for different combinations of full two-way streams with an initial payload.
Only a single stream is created between two machines - and there is, as such, no
server/client relation since both sides can initiate and handle requests. Which server
initiates the request is decided deterministically on the server names.
Requests are made through a mux client and server, which handles message
passing, congestion, cancelation, timeouts, etc.
If a connection is lost, all requests are canceled, and the calling server will try
to reconnect. Registered handlers can operate directly on byte
slices or use a higher-level generics abstraction.
There is no versioning of handlers/clients, and incompatible changes should
be handled by adding new handlers.
The request path can be changed to a new one for any protocol changes.
First, all servers create a "Manager." The manager must know its address
as well as all remote addresses. This will manage all connections.
To get a connection to any remote, ask the manager to provide it given
the remote address using.
```
func (m *Manager) Connection(host string) *Connection
```
All serverside handlers must also be registered on the manager. This will
make sure that all incoming requests are served. The number of in-flight
requests and responses must also be given for streaming requests.
The "Connection" returned manages the mux-clients. Requests issued
to the connection will be sent to the remote.
* `func (c *Connection) Request(ctx context.Context, h HandlerID, req []byte) ([]byte, error)`
performs a single request and returns the result. Any deadline provided on the request is
forwarded to the server, and canceling the context will make the function return at once.
* `func (c *Connection) NewStream(ctx context.Context, h HandlerID, payload []byte) (st *Stream, err error)`
will initiate a remote call and send the initial payload.
```Go
// A Stream is a two-way stream.
// All responses *must* be read by the caller.
// If the call is canceled through the context,
//The appropriate error will be returned.
type Stream struct {
// Responses from the remote server.
// Channel will be closed after an error or when the remote closes.
// All responses *must* be read by the caller until either an error is returned or the channel is closed.
// Canceling the context will cause the context cancellation error to be returned.
Responses <-chan Response
// Requests sent to the server.
// If the handler is defined with 0 incoming capacity this will be nil.
// Channel *must* be closed to signal the end of the stream.
// If the request context is canceled, the stream will no longer process requests.
Requests chan<- []byte
}
type Response struct {
Msg []byte
Err error
}
```
There are generic versions of the server/client handlers that allow the use of type
safe implementations for data types that support msgpack marshal/unmarshal.
2023-11-20 20:09:35 -05:00
|
|
|
}
|
|
|
|
|
|
2024-04-23 13:15:52 -04:00
|
|
|
const _HandlerID_name = "handlerInvalidLockLockLockRLockLockUnlockLockRUnlockLockRefreshLockForceUnlockWalkDirStatVolDiskInfoNSScannerReadXLReadVersionDeleteFileDeleteVersionUpdateMetadataWriteMetadataCheckPartsRenameDataRenameFileReadAllServerVerifyTraceListenDeleteBucketMetadataLoadBucketMetadataReloadSiteReplicationConfigReloadPoolMetaStopRebalanceLoadRebalanceMetaLoadTransitionTierConfigDeletePolicyLoadPolicyLoadPolicyMappingDeleteServiceAccountLoadServiceAccountDeleteUserLoadUserLoadGroupHealBucketMakeBucketHeadBucketDeleteBucketGetMetricsGetResourceMetricsGetMemInfoGetProcInfoGetOSInfoGetPartitionsGetNetInfoGetCPUsServerInfoGetSysConfigGetSysServicesGetSysErrorsGetAllBucketStatsGetBucketStatsGetSRMetricsGetPeerMetricsGetMetacacheListingUpdateMetacacheListingGetPeerBucketMetricsStorageInfoConsoleLogListDirGetLocksBackgroundHealStatusGetLastDayTierStatsSignalServiceGetBandwidthWriteAllListBucketsRenameDataInlineRenameData2handlerTesthandlerTest2handlerLast"
|
perf: websocket grid connectivity for all internode communication (#18461)
This PR adds a WebSocket grid feature that allows servers to communicate via
a single two-way connection.
There are two request types:
* Single requests, which are `[]byte => ([]byte, error)`. This is for efficient small
roundtrips with small payloads.
* Streaming requests which are `[]byte, chan []byte => chan []byte (and error)`,
which allows for different combinations of full two-way streams with an initial payload.
Only a single stream is created between two machines - and there is, as such, no
server/client relation since both sides can initiate and handle requests. Which server
initiates the request is decided deterministically on the server names.
Requests are made through a mux client and server, which handles message
passing, congestion, cancelation, timeouts, etc.
If a connection is lost, all requests are canceled, and the calling server will try
to reconnect. Registered handlers can operate directly on byte
slices or use a higher-level generics abstraction.
There is no versioning of handlers/clients, and incompatible changes should
be handled by adding new handlers.
The request path can be changed to a new one for any protocol changes.
First, all servers create a "Manager." The manager must know its address
as well as all remote addresses. This will manage all connections.
To get a connection to any remote, ask the manager to provide it given
the remote address using.
```
func (m *Manager) Connection(host string) *Connection
```
All serverside handlers must also be registered on the manager. This will
make sure that all incoming requests are served. The number of in-flight
requests and responses must also be given for streaming requests.
The "Connection" returned manages the mux-clients. Requests issued
to the connection will be sent to the remote.
* `func (c *Connection) Request(ctx context.Context, h HandlerID, req []byte) ([]byte, error)`
performs a single request and returns the result. Any deadline provided on the request is
forwarded to the server, and canceling the context will make the function return at once.
* `func (c *Connection) NewStream(ctx context.Context, h HandlerID, payload []byte) (st *Stream, err error)`
will initiate a remote call and send the initial payload.
```Go
// A Stream is a two-way stream.
// All responses *must* be read by the caller.
// If the call is canceled through the context,
//The appropriate error will be returned.
type Stream struct {
// Responses from the remote server.
// Channel will be closed after an error or when the remote closes.
// All responses *must* be read by the caller until either an error is returned or the channel is closed.
// Canceling the context will cause the context cancellation error to be returned.
Responses <-chan Response
// Requests sent to the server.
// If the handler is defined with 0 incoming capacity this will be nil.
// Channel *must* be closed to signal the end of the stream.
// If the request context is canceled, the stream will no longer process requests.
Requests chan<- []byte
}
type Response struct {
Msg []byte
Err error
}
```
There are generic versions of the server/client handlers that allow the use of type
safe implementations for data types that support msgpack marshal/unmarshal.
2023-11-20 20:09:35 -05:00
|
|
|
|
2024-04-23 13:15:52 -04:00
|
|
|
var _HandlerID_index = [...]uint16{0, 14, 22, 31, 41, 52, 63, 78, 85, 92, 100, 109, 115, 126, 136, 149, 163, 176, 186, 196, 206, 213, 225, 230, 236, 256, 274, 301, 315, 328, 345, 369, 381, 391, 408, 428, 446, 456, 464, 473, 483, 493, 503, 515, 525, 543, 553, 564, 573, 586, 596, 603, 613, 625, 639, 651, 668, 682, 694, 708, 727, 749, 769, 780, 790, 797, 805, 825, 844, 857, 869, 877, 888, 904, 915, 926, 938, 949}
|
perf: websocket grid connectivity for all internode communication (#18461)
This PR adds a WebSocket grid feature that allows servers to communicate via
a single two-way connection.
There are two request types:
* Single requests, which are `[]byte => ([]byte, error)`. This is for efficient small
roundtrips with small payloads.
* Streaming requests which are `[]byte, chan []byte => chan []byte (and error)`,
which allows for different combinations of full two-way streams with an initial payload.
Only a single stream is created between two machines - and there is, as such, no
server/client relation since both sides can initiate and handle requests. Which server
initiates the request is decided deterministically on the server names.
Requests are made through a mux client and server, which handles message
passing, congestion, cancelation, timeouts, etc.
If a connection is lost, all requests are canceled, and the calling server will try
to reconnect. Registered handlers can operate directly on byte
slices or use a higher-level generics abstraction.
There is no versioning of handlers/clients, and incompatible changes should
be handled by adding new handlers.
The request path can be changed to a new one for any protocol changes.
First, all servers create a "Manager." The manager must know its address
as well as all remote addresses. This will manage all connections.
To get a connection to any remote, ask the manager to provide it given
the remote address using.
```
func (m *Manager) Connection(host string) *Connection
```
All serverside handlers must also be registered on the manager. This will
make sure that all incoming requests are served. The number of in-flight
requests and responses must also be given for streaming requests.
The "Connection" returned manages the mux-clients. Requests issued
to the connection will be sent to the remote.
* `func (c *Connection) Request(ctx context.Context, h HandlerID, req []byte) ([]byte, error)`
performs a single request and returns the result. Any deadline provided on the request is
forwarded to the server, and canceling the context will make the function return at once.
* `func (c *Connection) NewStream(ctx context.Context, h HandlerID, payload []byte) (st *Stream, err error)`
will initiate a remote call and send the initial payload.
```Go
// A Stream is a two-way stream.
// All responses *must* be read by the caller.
// If the call is canceled through the context,
//The appropriate error will be returned.
type Stream struct {
// Responses from the remote server.
// Channel will be closed after an error or when the remote closes.
// All responses *must* be read by the caller until either an error is returned or the channel is closed.
// Canceling the context will cause the context cancellation error to be returned.
Responses <-chan Response
// Requests sent to the server.
// If the handler is defined with 0 incoming capacity this will be nil.
// Channel *must* be closed to signal the end of the stream.
// If the request context is canceled, the stream will no longer process requests.
Requests chan<- []byte
}
type Response struct {
Msg []byte
Err error
}
```
There are generic versions of the server/client handlers that allow the use of type
safe implementations for data types that support msgpack marshal/unmarshal.
2023-11-20 20:09:35 -05:00
|
|
|
|
|
|
|
|
func (i HandlerID) String() string {
|
|
|
|
|
if i >= HandlerID(len(_HandlerID_index)-1) {
|
|
|
|
|
return "HandlerID(" + strconv.FormatInt(int64(i), 10) + ")"
|
|
|
|
|
}
|
|
|
|
|
return _HandlerID_name[_HandlerID_index[i]:_HandlerID_index[i+1]]
|
|
|
|
|
}
|
