And if we use fileconfigure regions.json to apply the configuration, it will throw ERROR: An unknown error occurred (4000). We have confirmed that with an invalid json, it will throw ERROR: Invalid JSON while with a non-exist file it will throw ERROR: File could not be read (1513).
So it looks like there are some errors about the configuration, but we cannot figure it out. As there are really limited documentations about this.
That error means we aren’t properly dealing with some error condition internally. We should try to get it working for you, and then we can work on fixing the error message once we know what’s going wrong.
I notice that there are trailing commas after priority in “EA1” and US1". What happens if you remove those?
I think the reason for the unknown error is that this isn’t a valid json document (it can be made one by enclosing everything in {}). I tried doing that and then got an “Invalid JSON” error for the extra commas. When I removed those, I got an internal error for not having configured datacenter IDs on my cluster. It sounds like we have some work to do to polish this command and more clearly document it, but maybe you can try doing the above and seeing how it goes? I’ll also try configuring my cluster with datacenters and see if I can make more progress.
Not sure, I got the same thing but couldn’t explain it. I’ll have to get back to you on that one. I was able to get it to go through by forcing it, though I won’t explicitly recommend that without knowing why it thinks there’s a problem.
I think the problem here is that there are storage servers running in the satellite datacenters, but the expectation is that there won’t be any (storage should only be in primary datacenters). It may be helpful to follow the sequence of steps here for migrating from a single datacenter cluster to one configure with regions, which hopefully will avoid any of these weird cases.
I’m not sure if it’s necessary to set the machine class in satellites, but if you do I think all you’d need are transaction class processes.