Support generation of multiple MIO config files

Question

Support generation of multiple MIO config files

Closed this issue 2 years ago · 11 comments

c0appzrcgen and motraddr.sh should support generating multiple config files for MIO in one call. Suggested usage:

motradd.sh --mio 3 config1 config21 config42

to obtain 3 different configs under the specified file names.

Answer 1 · 2021-07-26T15:01:10.000Z

@u-u-h , This is now implemented and available on the SAGE cluster. Please check, and let me know if this works as you expected.

umanesan1@client-24~[1001]motraddr.sh --mio 3 a.txt b.txt
Illeg number of arguments!
umanesan1@client-24~[1002]motraddr.sh --mio 3 a.txt b.txt c.txt
umanesan1@client-24~[1005]cat a.txt b.txt c.txt | grep INST
  MOTR_INST_ADDR: 172.18.1.24@o2ib:12345:4:1
  MOTR_INST_ADDR: 172.18.1.24@o2ib:12345:4:2
  MOTR_INST_ADDR: 172.18.1.24@o2ib:12345:4:3
umanesan1@client-24~[1006]

Answer 2 · 2021-08-03T14:45:32.000Z

Seems to work on sage, startup time of mio is really long though.

Answer 3 · 2021-08-03T15:59:27.000Z

@u-u-h , do you mean the mio_init() taking approximately 40sec on Sage? We are working on fixing it.

Answer 4 · 2021-08-03T16:01:35.000Z

Yes. I didn't time it, just thought it was very long.

Answer 5 · 2021-08-03T16:32:09.000Z

Thanks for the confirmation. Yes, the clovis_init() function (now called m0client_init) takes a lot of time to complete. This affects all motr apps on Sage. Working on fixing it. Thanks.

Answer 6 · 2022-01-06T16:01:38.000Z

Hi @u-u-h and @nezzzu is this issue resolved? It seems that this issue can be closed as SAGE is now over? Is this issue still relevant?

Answer 7 · 2022-01-06T16:25:41.000Z

The issue of slow startup (#41) is still not solved as far as I can see (it's better, but not good).
Generating multiple configurations worked on sage; I have not checked if the upstream version on a system other than sage though.

Answer 8 · 2022-01-06T16:28:46.000Z

Ok I will label this issue as backlog as I know there was work being done on this issue.

Answer 9 · 2022-04-28T10:24:26.000Z

@u-u-h , @hessio - Is this still valid issue?

Answer 10 · 2022-08-25T10:27:17.000Z

ganesan umanesan commented in Jira Server:

[~530903] This particular issue is fixed as can be seen from my first comments.

Answer 11 · 2022-08-25T11:30:46.000Z

Chandradhar Raval commented in Jira Server:

Marking this JIRA Closed as per confirmation from [~519680]