Ok. If proxy exist in cluster (configured etc) and dashboard stop. Proxy can't re register in cluster, no matter use I etcd or filesystem. Maybe I was made not right cluster, but ft or ha can't exist without auto re register proxy. One more thing if I running set/get command I getting error: router is not online if use sentinel and stopped dashboard.

Currently, there are no clear guidelines for determining when to log messages and what category to give them. We need to address the following, to begin with:

• Distinguishing TRACE vs. DEBUG messages.
• What events should be logged with INFO messages?
• When actions fail:
  • When to throw an exception and when to log.
  • When to WARN vs. when to log an ERROR.

Disclaimer: This is a bot

It looks like your repo is trending. The github_trending_videos Instgram account automatically shows the demo gifs of trending repos in Github.

Your README doesn't seem to have any demo gifs. Add one and the next time the parser runs it will pick it up and post it on its Instagram feed. If you don't want to just

http://localhost:22222/ping returns OK regardless of Redis status (e.g. when all Redis nodes are stopped). This behavior contradicts the documentation:

ping: performs a Redis inline ping to test Dynomite and storage

Referenced line: https://github.com/nosqlclient/nosqlclient/blob/32347b61058874a41a1d2707432fbc6a1b50c258/client/imports/views/pages/database_stats/database_stats.html#L207

ATM nosqlclient deployed to a subdirectory with valid ROOT_URL

By default, sending multiple constraints to upper.io Find() behaves as a union (OR), which may surprise users expecting an intersection (AND). Can we make this default behavior more clear in the documentation and examples?

I'm not sure how feasible this may be, but the old logparser program from Microsoft supported queries like

Select * from test.csv

And it would read from test.csv, without needing any config files.

A common scenario is when you want to adjust the default dataset rather than setting it up from scratch, that's why it will be convenient when the default dataset is available within the Relation.dataset configuration block.

Probably the best way to do this is to tweak Gateway#dataset so that it can also accept a schema because we have it available already when dataset is retrieved from t

there should be two mode in a table:
normal mode: level0 number limit is 20; score is num / 2
init mode: level0 number limit is 20000; score is (root of num) / 2