redis-port | A service automatically syncing Redis data into RebornDB | Database library

I've just tried this approach locally using spring-geode-starter:1.3.0.RELEASE and it seems to be working just fine:

Redis is not using HTTP protocol for client connection. So any http client like CURL cannot directly communicate with Redis server.

You can use redis-cli for testing

The method ray.services.check_and_update_resources is an internal method and not intended to be exposed. You can check the cluster resources with ray.global_state.cluster_resources() as well as ray.global_state.client_table().

Thanks for suren's answer.

But i think redis.basic.svc.cluster.local is outside DNS host to match by VirtualService, and VirtualService.host is route to service redis-svc with full namespace path.

Maybe not for that reason.

bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell

Generally, these are harmless errors.

This other Stack Exchange thread might help, since you are using a custom /tmp dir for data:

The simple way to do this is to run systemctl edit redis. This will create an override drop-in file /etc/systemd/system/redis.service.d/override.conf, in which you can place your changes (and the proper section):

[Service] ReadWriteDirectories=-/my/custom/data/dir

You may also create that directory and place files ending in .conf in it manually. But do not leave the directory empty, as this will disable the service.

In either case, run systemctl daemon-reload and you are ready to restart your service.

Many threads also point to filesystem inconsistency as root cause. Since you are using EC2, check this AWS forums post:

To fix this, you will have to:

1. Stop the instance

2. Detach the root volume of your instance

3. Attach the volume as a data volume to any running Linux instance in the same availability zone

4. Perform a filesystem check (fsck) on the volume and fix the issues

5. Detach the volume and attach it back to your instance as it's root volume

6. Boot back instance and verify if the volume was able to mount successfully

As a last resort, terminate the instance if possible.

Hope it helps!

This is the ui today (Aug, 2019). The docs are outdated with the UI pictures it seems.

Just in case anyone in the future has similar question.

I ran a slightly modified version of the config you posted, and this works for me

Here's a minimal example.

In the more verbose examples, the defaults should be good so you shouldn't need to change very much.

Also, if you already have a Ray cluster running and you started it with the autoscaler, you can submit jobs via ray exec, see the relevant documentation. See this script for an example of how to use it.