storj/storage
ccase 38f707c0d2
storage/redis: Limit should not be applied as count.
COUNT on a SCAN does not actually limit the results [1]. It limits the
amount of work a single call to SCAN will perform before returning. By
setting this to limit we can sometimes timeout on the request if limit
is very large.

This restores storage/redis back to it's original behavior.

[1]: https://redis.io/commands/scan#the-count-option

Change-Id: Ia75afb5152df909df38c9a7c6feb74d062f49d6a
2020-01-22 13:23:06 -05:00
..
boltdb storage: Plumb limit through storage backends. 2020-01-19 21:23:20 +00:00
cockroachkv private/tagsql,storage: fixes to context cancellation 2020-01-20 15:44:39 +02:00
filestore common: separate repository 2019-12-27 14:11:15 +02:00
postgreskv storage/postgreskv: Reverting back to the venerable PG CAS 2020-01-22 11:36:25 -05:00
redis storage/redis: Limit should not be applied as count. 2020-01-22 13:23:06 -05:00
storelogger storage/: remove reverse-key-listing feature 2019-11-12 18:47:51 +00:00
teststore lint: add staticcheck as a separate step (#3569) 2019-11-14 10:31:30 +02:00
testsuite common: separate repository 2019-12-27 14:11:15 +02:00
blob.go storagenode: Include trash space when calculating space used 2019-12-23 19:07:03 -07:00
common.go storage: Plumb limit through storage backends. 2020-01-19 21:23:20 +00:00
iterator.go storage/: remove reverse-key-listing feature 2019-11-12 18:47:51 +00:00
listkeys.go Stylistic Go Cleanup (#2524) 2019-07-22 15:10:04 -04:00
listv2.go storage: Plumb limit through storage backends. 2020-01-19 21:23:20 +00:00
util.go storage: add monkit task to missing places (#2122) 2019-06-05 16:23:10 +02:00