Hi there, Any errors in the engine logs? Cheers, Johann From:<daos@daos.groups.io> on behalf of Peter <magpiesaresoawesome@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date:

Hi All, I would like to highlight a new API we added in 1.2 in regards to object class selection when generating OIDs for

All, We are pleased to announce that DAOS 1.2 release was completed on Friday, and is now generally available. This release brings support for the following features: Per-container ACL Improved

Yes, it is. -- Regards, Nasf

So the leader is the coordinator of 2PC?

The description in the VOS README was for single redundancy group based DAOS transaction, at that time, we did not supported distributed transaction that may touch multiple redundancy groups. We will

hi～ There are two different leader election rules in the code comments and in the VOS readme, as shown below. Does the leader described by the two have the same meaning? According to my

Hello Joel, Thanks to you, all my problems have been solved. Best Regards, Erika

Hello Erika, I saw a similar issue and the same failure signature with the v1.1.3 build with verbs on Mellanox. I’d like you to try upgrading your OFI to a more modern version. The version

Hello DAOS Community, I'm having trouble running DAOS v1.1.3 on Centos 7.9. I'm trying to run a server and a client on a single node. After formatting the DCPM, when I try to start the server, I

Hello DAOS developers and users, I am trying to start a DAOS server of a centos 7 virtual machine for tests. I used RPMs version 1.0.3 from the Intel website and tmpfs for /mnt/daos. If I try to

If the old DTX leader crashed after all participants ‘prepared’ but some of them not ‘committed’ yet, then the remaining alive DTX participants will elect new leader based on some algorithm.

hi~ I have some questions about DTX. In DAOS, DTX is used to implement distributed transactions and ensure replica consistency. As far as I know, for a transaction in a prepared state in a

Sure thing. Unless you say otherwise, I’m planning to submit it against 1.2 and 2.0 branches. https://github.com/daos-stack/daos/pull/5246

Hi Steffen, Good catch! It sounds like we need to add a “LimitNOFILE” entry to our daos_server’s systemd unit file. @Rosenzweig, Joel B could you please take of this? Thanks in advance.

A final "Hi" on that topic, we have discovered the reason for the issue: The ulimit on the _server_ side was too low and it differs between regular users and daemons like the DAOS server. For the

Hi again once more, meanwhile we checked the 'tcp' and the 'verbs' provider. For 'tcp' we also experience the timeouts and an subsequently unusable DAOS system. For 'verbs' (on an OmniPath network)

Hi again, Here is the output of a failed attempt to run IOR. It now crashed for 48 processes on a single client. For smaller process counts IOR succeeds with the same messages/warnings from

Hi Alex, Thanks for that input, we'll try to reproduce the issue with those settings and provide them ASAP. Sure. client $ ulimit -a core file size (blocks, -c) 0 data seg size

Hi Steffen, Could you enable OFI level logs by setting FI_LOG_LEVEL=warn on the client side and provide stdout/stderr output from runs that result in mercury erorrs/timeouts? Also can you tell us