Hello, Colin Sure, I will work on the patch sooner. Thanks WangDi From: <daos@daos.groups.io> on behalf of Colin Ngam <colin.ngam@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date:

Hello WangDi, Thanks for your response. May be the Priority should be higher than 4-LOW? Although we are still in testing environment. Thanks. Colin From: <daos@daos.groups.io> on

Hello, Replied inline. From: <daos@daos.groups.io> on behalf of Colin Ngam <colin.ngam@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date: Monday, April 13, 2020 at 10:40 AM To:

Joel, I came to the same conclusion, sorry for wasting your time. There is currently an issue where the daos_io_server dies immediately because it can’t find its own librdb.so module,

Hi, I rebooted 2 hosts. Restarted the access_host server before restarting the other hosts. Here’s the log: daos_io_server:1 04/13-12:24:09.73 delphi-006 a8a27db9: rank 1 became pool

Hi Kevan, I ran your test locally in my environment on master and it encountered no issues. Figures, right? I spent some time looking at the auto-generated code to see what it is doing. I

Hi, Colin Unfortunately daos_perf supports only DAOS fetch/update APIs so far, there are IOR and FIO plugin runs over DAOS array API, but I’m not aware of any benchmark using daos_kv_put().

Joel, Thanks for the explanation below, makes sense. Can’t wait for that code to land. Back to the problem at hand; now I am even more confused…. I borrowed one of my compatriot’s

Hi Kevan, You are right that it won’t help a client to know the interface and domain names of the server. In this case, we’re not actually sending the server’s interface and domain in the

Joel, I’m curious; how does it help a client to know the interface and domain names of this server? I can’t see how the client could possibly use them. Anyway, back to the problem. I

Greetings Niu, Daos_perf does not support DAOS Simple KV interfaces e.g. daos_kv_put? Is there another performance utility that does? Thanks. Colin

Yes, I agree with you, and I’ve pasted your findings in DAOS-4521 and we’ll fix it along with problem of verification failure in SV mode. Thanks a lot! Thanks -Niu

The env is only read once on server start (actually, you can put it in server yaml file just like other env variables), so it can’t be set dynamically so far. Thanks -Niu

That’s good information. I added the “interface” field and some others last week as we are expanding the capabilities of the GetAttachInfo message to help automatically configure the clients.

Joel, I am still chasing this. Problem is occurring in the server in routine ds_mgmt_drpc_get_attach_info. Routine ds_mgmt_get_attach_info_handler() fills in ‘resp’ with nsprs and the psrs

Actually, we are not - There was some confusion on that point. Kevan is running latest master, I accidentally wound up a week out of date. So I assume if I updated, I would have the same

Are you both running the same build?

Sigh. Please ignore this, one of my compatriots with the same hardware config was able to create this pool and container without error. So the problem is obviously in my setup. Kevan From:

Greetings, Recently I updated my daos repo to master top of tree, and now any attempt to create a container causes the access-point daos_io_server to segfault. Before I dig deeply, is this a

Greetings, Is there an Object Array performance test available? I do not see this support in daos_perf. Thanks. Colin