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.

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

asd-discovery detects asds from another env and tries to connect while it shouldn't #269

Closed
pploegaert opened this issue Jun 29, 2016 · 6 comments

Comments

@pploegaert
Copy link

pploegaert commented Jun 29, 2016

asd-discovery process detects asds belonging to another alba and tries to connect but it doesn't have the hardware required to do that
To be investigated

alba asd-discovery
....
        total = 102621958144L; used = 7737179L }) ; ips = ["172.23.154.231"]; port = (Some 8003) ; tlsPort = None ; useRdma = true ; }
{extras: (Some { Discovery.node_id = "1b2e6925_0"; version = "AsdV1";
        total = 102621958144L; used = 10915628L }) ; ips = ["172.23.154.231"]; port = (Some 8001) ; tlsPort = None ; useRdma = true ; }
....
2016-06-29 09:37:57 138539 +0200 - allflash184 - 28768/0 - alba/proxy - 1016994 - debug - Error during check osd claimed thread (for 8000_00_1b2e6925): (Unix.Unix_error "No such device" socket ""); backtrace:; Raised at file "format.ml", line 185, characters 41-52; Called from file "format.ml", line 427, characters 6-24
@domsj
Copy link
Contributor

domsj commented Jul 1, 2016

This behaviour was in the past considered as a feature ...
Disabling it (either by default or entirely) would be a backwards compatibility breaking change for alba.
But it can be done if first some changes are made to the framework.

@wimpers
Copy link

wimpers commented Jul 5, 2016

Please lay your egg what should be done.

@saelbrec
Copy link
Contributor

From the FWK point of view this isn't used anymore for Alba ASD's, but what in case of Kinetic, @toolslive ? This will have to be re-introduced?

@toolslive
Copy link
Member

For Kinetic, this isn't an issue as you'll always have the hardware to connect to the drive you've discovered: It's always ethernet.
A possible solution is that a component (proxy/maintenance) could be given the extra information that it has rdma capable hardware at startup time (configuration/flag) and use that information before trying to connect to rdma based ASDs.

@domsj
Copy link
Contributor

domsj commented Nov 15, 2016

If I understand correctly no further solution is needed (for how deployments are currently done by the framework).
Asds and Kinetics are both only configured to NOT use rdma, so all proxies/maintenance should be able to connect to any asd/kinetic.

@toolslive
Copy link
Member

Indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants