Redis cluster fail with no apparent node seen in failed state

[Lax kota]

When I run 'cluster nodes' lists all nodes in good state(none were seen in failed state), but when I try to write to the cluster I get 'CLUSTERDOWN' error. Is there any way to know why the cluster is down. 

Here is o/p of my cluster nodes cmd:

9a16efc1ddd11818833cea819958b49f4e61e7da 192.168.50.201:6379 master - 0 1461104642412 1518 connected

ebe380402445c37f18829272860fc386cc682093 192.168.50.42:6379 master - 0 1461104642412 0 connected

685c20761681087d6720fac5e523eab5d8e9bada 192.168.50.20:6379 slave b9b6b5660663cb87c1fd11aea2adfc90db9c6563 0 1461104643414 1516 connected

fb50845383a895efcbd483fa7a4d5367956c2908 192.168.50.19:6379 slave - 0 1461104644420 1514 connected

ae270be8dee8122368b172cb3032a80081343be8 192.168.50.48:6379 master - 0 1461104642913 1517 connected

b9b6b5660663cb87c1fd11aea2adfc90db9c6563 192.168.50.155:6379 myself,master - 0 0 1516 connected

O/P of 'cluster info' cmd:

cluster_state:fail

cluster_slots_assigned:0

cluster_slots_ok:0

cluster_slots_pfail:0

cluster_slots_fail:0

cluster_known_nodes:6

cluster_size:0

cluster_current_epoch:1518

cluster_my_epoch:1516

cluster_stats_messages_sent:798

cluster_stats_messages_received:798

Thanks

Lax

[Tuco]

You need to assign all the 16384 slots in the cluster, only then the cluster state will become ok....

as of now, your cluster does not know which node to send a particular key to.

See this link, where the cluster is created using redis-trib.rb.

[Lax kota]

Thanks for response. Yeah, figured it out. In my case cluster nodes went down and came back up. In the process ended up having 0 slots. Doing 'redis-trib.rb fix' helped resolve in my case.

Thanks
Lax