I did look into your logs and notice messages like “Could not lookup ofi+sockets://11.11.200.48:31416” which mean that sockets URIs (instead of tcp) are still registered and storage nodes haven’t
registered the new tcp-based URIs yet. Please make sure to stop the servers, umount /mnt/daos* (and wipefs -a /dev/pmem* if you use pmem) before restarting the servers.
Cheers,
Johann
From:
<daos@daos.groups.io> on behalf of "ping.wong via groups.io" <ping.wong@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date: Wednesday 3 February 2021 at 17:05 To: "daos@daos.groups.io" <daos@daos.groups.io> Subject: Re: [daos] Client application single value KV Put high latency using multiple threads (pthread)
Hi Johann,
I did reformat and restart all agents on client node and the two servers. Both servers using ofi+tcp;ofi_rxm provider start fine; however, the client application failed. Please refer the errors in my previous email (marked with ****). For now, I can only
get ofi+sockets provider to work reliably. Are there any addition parameter settings in any of the yaml file (daos_server.yml, daos_control.yml, daos_agent.yml etc.) that I need to change beside switching from ofi+sockets to ofi+tcp;ofi_rxm? Any other environment
variables to set?
Ping
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
