conent of /tmp/server0.log shown below: Maybe the swim_progress() SWIM shutdown give me some tips, maybe not. Another question, in the storage cluster, I have 3 nodes(snode1, snode2, snode3), and I

Greetings, Does it work with –svc 1? Thanks. Colin From: <daos@daos.groups.io> on behalf of "Nabarro, Tom" <tom.nabarro@...> Reply-To: "daos@daos.groups.io"

You probably need the server log from the access point rank (/tmp/server0.log default setting in server config) to help debug the issue. Tom

HI Guys: As shown below, when I try to create container with POSIX type, the admin terminal blocked there(top screenshot). another terminal lauched the DAOS cluster with clush cmd just showed that

Johann, thx for your response. I have resolved this problem. the problem is that I filled in the wrong provder option in daos_server.yml file. Actually, I do figure out the proble from the log fille.

Hi Pittman, Thanks for the info. Please let me know when your ticket is done. I’ll move the attributes from UNS path to container. Thanks.

Assume “CPU threads” you mean HyperThread core. Yes I mean CPU cores, now in DAOS there is only one place using CPU HyperThreading cores that is for system XS (RDB XS and drpc XS), all other XS

Hi Xuezhao, You mean CPU Cores and not CPU threads? Thanks. Colin From: <daos@daos.groups.io> on behalf of "Liu, Xuezhao" <xuezhao.liu@...> Reply-To: "daos@daos.groups.io"

Hi WangDi, commit 8200a7fb403e091b51b4b00c1aec57dafefb1ada [daos@hl-d106 scripts]$ daos pool list-cont --pool 96670dea-d357-4235-8659-dac16d01b1c2 --svc 40 [daos@hl-d106 scripts]$ … No

Hi, Server_group certainly seems a useful thing to add, service ranks I thought was scheduled for removal but would also make sense if it’s still in use. I can file a ticket and work on this as

Hi Colin, If the #cores is enough, to get best performance commonly can configure with one helper XS for each VOS target – in your case can setnr_xs_helpers as 16 if you configured with 16

Hi Guys, Currently, there are only three info set to duns attribute of UNS path. They are FS type, pool UUID and container UUID. It’s enough for dfuse since dfuse’s server group and service

Greetings, We currently set nr_xs_helpers to 0. We have defined 16 targets. That’s per daos_io_server. For best performance, what value should nr_xs_helpers be set? Also, consideration like

Hello, Colin I tried with this commit, and it can generate the failure message on my env. I assume you build the source yourself? And what is your output of “ldd install/bin/daos” ? Thanks WangDi

Greetings, commit 8200a7fb403e091b51b4b00c1aec57dafefb1ada Thanks. Colin From: <daos@daos.groups.io> on behalf of "Wang, Di" <di.wang@...> Reply-To: "daos@daos.groups.io"

Hello, Thanks. This does show the connection failed with –svc 40. I am not sure why it does not output any failure messages. But I do see others also complained about zero failure message. Which

Hi WangDi, Is this what you need: 05/14-09:53:00.86 hl-d106 DAOS[20928/20928] fi INFO src/cart/src/gurt/fault_inject.c:486 d_fault_inject_init() No config file, fault injection is

Hello Patrick, Well, this is really strange indeed. BTW, I am unable to reproduce when running with current master which is only 45 commits ahead of yours and none seem to be related… If problem

Hi, thanks for the tip! It seems that a "regular dmg storage format" doesn't do the trick, but appending "--reformat" resolves the issue. It runs fine now. Kind regards Ruben Am 14.05.20 um 09:02

Hi, I assume that you have run dmg storage format after starting the server and before creating the pool, right? If you don’t want to emulate any SSD, you should also comment out the bdev_*