You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
/v1/status return null after restarting sched, and the fact is that all the redis instances are still running in mesos agents, to fix this, I have to manually run "curl ip:5656/v1/STATUS/sdb_test" to get redis "sdb_test" information, this call returns information, then "curl ip:5656/v1/STATUS" call returns sdb_test redis information, so there is something wrong in the /v1/STATUS call, it's not working as expected.
The text was updated successfully, but these errors were encountered:
From the code, it seems typ.MemDb.I is nil when restarting scheduler, just wondering why the instances are not loading from DB (in my case, it's zk) after restarting, is this a bug?
Hi,
/v1/status return null after restarting sched, and the fact is that all the redis instances are still running in mesos agents, to fix this, I have to manually run "curl ip:5656/v1/STATUS/sdb_test" to get redis "sdb_test" information, this call returns information, then "curl ip:5656/v1/STATUS" call returns sdb_test redis information, so there is something wrong in the /v1/STATUS call, it's not working as expected.
The text was updated successfully, but these errors were encountered: