Ray memory not working on ray1.4 deployed on minikube

Hello I am trying to run ray memory on minikube with ray 1.4, I get the below message:

$ ray memory
[2021-06-17 15:01:21,143 W 2608129 2608129] redis_context.cc:338: Will retry in 100 milliseconds. Each retry takes about two minutes.
[2021-06-17 15:01:24,215 W 2608129 2608129] redis_context.cc:338: Will retry in 100 milliseconds. Each retry takes about two minutes.
[2021-06-17 15:01:27,287 W 2608129 2608129] redis_context.cc:338: Will retry in 100 milliseconds. Each retry takes about two minutes.
[2021-06-17 15:01:30,359 W 2608129 2608129] redis_context.cc:338: Will retry in 100 milliseconds. Each retry takes about two minutes.
^C[2021-06-17 15:01:31,081 W 2608129 2608129] redis_context.cc:338: Will retry in 100 milliseconds. Each retry takes about two minutes.
^C[2021-06-17 15:01:31,471 W 2608129 2608129] redis_context.cc:338: Will retry in 100 milliseconds. Each retry takes about two minutes.
^C[2021-06-17 15:01:31,696 W 2608129 2608129] redis_context.cc:338: Will retry in 100 milliseconds. Each retry takes about two minutes.

any suggestions?

cc @Dmitri, any ideas about this?

I’m unable to reproduce this with the default Helm configuration.
Could you post a github issue with reproduction details so we can track this?

@Dmitri even I am not unable to reproduce, I suspect it has to be with bad conda env ie I imay nstalled too many dependencies with pip in a conda env which may have caused this issue

hmm, ok – we’ll watch out for this!