Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MktreeError: Error creating directory #382

Closed
Satbek opened this issue Nov 29, 2019 · 0 comments · Fixed by #381
Closed

MktreeError: Error creating directory #382

Satbek opened this issue Nov 29, 2019 · 0 comments · Fixed by #381

Comments

@Satbek
Copy link
Contributor

Satbek commented Nov 29, 2019

I use cartridge 1.0.0 and cartridge-cli 1.2.1

If I start app with this instances.yml config

eav.api:
  workdir: ./tmp/db/3301/
  http_port: 8081
  advertise_uri: "localhost:3301"

eav.s1-master:
  workdir: ./tmp/db/3302/
  http_port: 8082
  advertise_uri: "localhost:3302"

eav.s1-replica:
  workdir: ./tmp/db/3303/
  http_port: 8083
  advertise_uri: "localhost:3303"

eav.s2-master:
  workdir: ./tmp/db/3304/
  http_port: 8084
  advertise_uri: "localhost:3304"

eav.s2-replica:
  workdir: ./tmp/db/3305/
  http_port: 8085
  advertise_uri: "localhost:3305"

i will get this errors on some instances:

s1-master | /Users/s.turganbayev/work/eav/init.lua:20: MktreeError: Error creating directory "/Users/s.turganbayev/work/eav/test/stress/tmp/db": File exists
s1-master | stack traceback:
s1-master |     ...ayev/work/eav/.rocks/share/tarantool/cartridge/utils.lua:116: in function 'mktree'
s1-master |     ...urganbayev/work/eav/.rocks/share/tarantool/cartridge.lua:268: in function 'cfg'
s1-master |     /Users/s.turganbayev/work/eav/init.lua:9: in main chunk
s2-replica | Using advertise_uri "localhost:3305"

I think this is because of race-condition between tarantool instances. And cartridge-cli may create workdirs for instances before starting them.

@rosik rosik transferred this issue from tarantool/cartridge-cli Dec 2, 2019
@rosik rosik closed this as completed in #381 Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant