Description
my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:
- 3.1.21
Mode:
- Single-Server
Storage-Engine:
- rocksdb
On this operating system:
- Linux
- CentOS 7 .rpm
Foxx
These are the steps to reproduce:
- send a req to http://127.0.0.1:8529/_db/yabco/yabco-service/rpc
- send a req to http://127.0.0.1:8529/_db/yabco-dev/yabco-service/rpc
- send a req to http://127.0.0.1:8529/_db/yabco/yabco-service/rpc
- the data is stored on yabco-dev instead of yabco
...
yabco-service on yabco, is running in production mode.
yabco-service on yabco-dev, is running in development mode.
0- create two services with mount points of /yabco-service on two different databases with different users, say yabco and yabco-dev.
---
To make sure its not from same name
To make sure that the error was not from me, I changed the second service name from yabco-service to yabco-service-dev.
now on yabco I have yabco-service
and on yabco-dev I have yabco-service-dev
UPDATE
Even changing the service name doesn't help!
I have to go and switch the service from prod to dev and again from dev to prod mode, so to make the data get stored in the correct Database!
What a nasty BUG! 👎