Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Multiple Gateways cannot be associated correctly to the same Service #9

Closed
canepat opened this issue Jul 1, 2016 · 2 comments
Closed

Multiple Gateways cannot be associated correctly to the same Service #9

canepat opened this issue Jul 1, 2016 · 2 comments
Assignees
@canepat
Labels
bug

Comments

@canepat
Copy link
Owner

canepat commented Jul 1, 2016

In order to have separate traffic back to Gateways then the Service needs separate endpoints for them. This can be done in different ways including configuration, a discovery service, or by using the Image.sourceIdentity() which can be picked up when a onAvailableImage() callback is triggered.
@canepat
Copy link
Owner Author

canepat commented Jul 1, 2016

For the request traffic to the same channel and stream id, the Header.sessionId() can be used to match request sources with responses previously matched up with the onAvailableImage() callbacks.

@canepat canepat added the bug label Jul 1, 2016
@canepat canepat self-assigned this Jul 1, 2016
@canepat
Copy link
Owner Author

canepat commented Jul 27, 2016

The addService and addGateway APIs in Helios class shall be modified to take as parameter just the input stream where the Aeron subscription takes place; the output streams shall be added to the Service or Gateway using the Aeron onAvailableImage() callback. The Service and Gateway implementations shall be modified to create output ring buffers and their processors accordingly, based on Image callback information (sourceIdentity, streamId, sessionId...).

canepat added a commit that referenced this issue Dec 17, 2016
@canepat
Added MMB Data message to correctly separate business and administrat…
abab29a 
…ive data messages

Added MMB Startup message to address application-level association between GWs and SVCs
Handled MMB Startup/Shutdown messages to address application-level association between GWs and SVCs as per issues #9 and #15
Changed some thread running variables to use volatile instead of atomic primitives
Added initial status counters support
Refactored report classes and functions
Added/modified unit and perf tests
@canepat canepat closed this as completed Dec 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@canepat canepat

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@canepat