<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi all,</div><div><br></div><div>We've come across an issue recently with Slurm account names. Our center uses fairly long Slurm account names, as they record various important pieces of information about the account such as the user's unique id, department, project name, etc. Consequently, our account naming structure is such that many accounts share a pretty lengthy common prefix. We've discovered that if two account names share a prefix of more than 20 characters, Slurm will error out and not add the account. We think this has to do with the sub_part for the name index set on the acct_table table (see below):<br></div><div><br></div>MariaDB [slurm_accounting]> show index from acct_table\G;<br>*************************** 1. row ***************************<br>        Table: acct_table<br>   Non_unique: 0<br>     Key_name: PRIMARY<br> Seq_in_index: 1<br>  Column_name: name<br>    Collation: A<br>  Cardinality: 14<br>     <b>Sub_part: 20</b><br>       Packed: NULL<br>         Null:<br>   Index_type: BTREE<br>      Comment:<br>Index_comment:<br>1 row in set (0.00 sec)<br><div><br></div><div>Can this be changed? Changing our account names to not share a common prefix would be difficult and cause problems with a lot of other software we use that is site-specific. We'd rather just remove the sub_part (accepting the performance implications).</div><div><br></div><div>Thanks,<br></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(7,55,99)"><font size="2">____</font></span></span><span style="color:rgb(7,55,99)"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif">_____</span></span></span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif">__________</span></span></span></span></span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif">__________</span></span></span></span></span></span></span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif"><span><span style="font-family:arial,helvetica,sans-serif">__________</span></span></span></span></span></span>_____</span></span>______<br><b>Jacob D. Chappell, CSM</b><br><b>Research Computing Associate</b><br>Research Computing | Research Computing Infrastructure<br>Information Technology Services | University of Kentucky<br><a href="mailto:jacob.chappell@uky.edu" target="_blank">jacob.chappell@uky.edu</a><br></span></font></span></div></div></div></div></div></div></div></div></div></div></div></div></div></div>