aboutsummaryrefslogtreecommitdiffstats
path: root/src/libserver/fuzzy_backend_redis.c
Commit message (Collapse)AuthorAgeFilesLines
* [Project] More reworkVsevolod Stakhov2019-06-221-54/+46
|
* [Project] First refactoring step libevent->libevVsevolod Stakhov2019-06-221-1/+1
|
* [Fix] Core: Fix address rotation bugVsevolod Stakhov2019-02-181-4/+4
| | | | | | | | | | | | | | | | | | | | | | Previously, upstream.get_addr function returned the new address of the upstream. Unfortunately, it was used for printing addresses. It caused the following situation: let's imagine we have A1 and A2 where A1 was initially selected. So the connection was performed to A1: Current addr Selected addr Connect+---------+ A2+------>A1 A1 | +-+Print failure<---+ A1+------>A2 A2 | +----+ +->Mark failure+-------->+ A2 | +----+ But the failure OP as well as log message told about `A2` where the real problem happened with `A1`. This commit adds distinguishing between getting the next and the current address of the upstream resolving this issue.
* [Project] Migrate fuzzy redis backend to lua_redisVsevolod Stakhov2018-11-231-98/+79
|
* [Minor] Fix event pending checksVsevolod Stakhov2018-10-061-1/+1
|
* [Minor] Optimise allocation size slightlyVsevolod Stakhov2018-07-161-7/+7
|
* [Fix] Plug memory leak in fuzzy updatesVsevolod Stakhov2018-07-161-4/+0
|
* [Feature] Add more extended statistics about fuzzy updatesVsevolod Stakhov2018-07-061-14/+32
|
* [Feature] Add logic to deduplicate updates queueVsevolod Stakhov2018-07-051-0/+6
|
* [Project] Update Redis backend to support refreshingVsevolod Stakhov2018-07-051-0/+84
|
* [Feature] Distinguish IP failures from connection failuresVsevolod Stakhov2018-07-021-9/+9
|
* [Project] Enable fast debug lookup for some modulesVsevolod Stakhov2018-01-201-2/+4
|
* [Minor] Add more diagnostic for fuzzy hashes lookupVsevolod Stakhov2017-11-251-7/+14
|
* [Rework] Implement new version of fuzzy repliesVsevolod Stakhov2017-11-251-11/+55
|
* [Fix] Do not try to connect to non-supported addressesVsevolod Stakhov2017-11-251-0/+4
|
* [Minor] More g_slice cleanupsVsevolod Stakhov2017-10-281-8/+9
|
* [Feature] Use array instead of queue to reduce memory fragmentationVsevolod Stakhov2017-08-171-6/+6
|
* [Minor] Allow to use numeric database when parsing redis paramsVsevolod Stakhov2017-06-241-1/+6
|
* [Fix] Fix issues with empty updatesVsevolod Stakhov2017-01-271-0/+6
|
* [Fix] Break pool connection on fatal redis errorsVsevolod Stakhov2017-01-171-20/+21
| | | | MFH: true
* [Fix] Fix possible memory corruption in redis poolVsevolod Stakhov2017-01-121-2/+2
| | | | MFH: true
* [Fix] Avoid extensive reallocsVsevolod Stakhov2017-01-121-21/+36
| | | | MFH: true
* [Fix] Fix argument returned on redis backend errorsVsevolod Stakhov2017-01-061-11/+11
| | | | MFH: true
* [Fix] Fix probability calculations for fuzzy redis backendVsevolod Stakhov2017-01-051-40/+46
|
* [CritFix] Do not trust remote shingles countVsevolod Stakhov2017-01-051-2/+1
| | | | MFH: true
* [Fix] Really fix redis shingles checkVsevolod Stakhov2016-11-051-2/+4
|
* [Fix] Fix extraction of shingles from redis fuzzy storageVsevolod Stakhov2016-11-051-5/+6
|
* [Minor] Add logging to the redis backend for fuzzyVsevolod Stakhov2016-09-051-0/+43
|
* [Minor] Fix multiple issues in redis fuzzy backendVsevolod Stakhov2016-09-051-9/+127
|
* [Minor] Implement the rest functions for redis fuzzy backendVsevolod Stakhov2016-09-051-9/+440
|
* [Minor] Implement checks in redis fuzzy backendVsevolod Stakhov2016-09-051-13/+379
|
* [Minor] Implement some features of redis backendVsevolod Stakhov2016-09-021-1/+261
|
* [Minor] Skeleton for redis fuzzy backendVsevolod Stakhov2016-09-021-0/+175