summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Diskless replication: missing listRewind() added.memsyncantirez2014-10-291-1/+5
| | | | | | | | | | This caused BGSAVE to be triggered a second time without any need when we switch from socket to disk target via the command CONFIG SET repl-diskless-sync no and there is already a slave waiting for the BGSAVE to start. Also comments clarified about what is happening.
* Log slave ip:port in more log messages.antirez2014-10-271-6/+11
|
* Use new slave name function for diskless repl reporting.antirez2014-10-271-4/+4
|
* Added a function to get slave name for logs.antirez2014-10-273-15/+29
|
* Diskless replication: log BGSAVE delay only when it is non-zero.antirez2014-10-271-1/+2
|
* Document repl-diskless-sync-delay in redis.conf.antirez2014-10-271-0/+12
|
* Diskless sync delay is now configurable.antirez2014-10-274-3/+17
|
* Remove duplicated log message about starting BGSAVE.antirez2014-10-241-1/+0
|
* Diskless replication documented inside example redis.conf.antirez2014-10-241-0/+27
|
* Diskless replication tested with the multiple slaves consistency test.antirez2014-10-241-64/+67
|
* Diskless replication: child -> parent communication improved.antirez2014-10-231-20/+34
| | | | | Child now reports full info to the parent including IDs of slaves in failure state and exit code.
* Translate rio fdset target EWOULDBLOCK error into ETIMEDOUT.antirez2014-10-221-1/+8
| | | | | | | EWOULDBLOCK with the fdset rio target is returned when we try to write but the send timeout socket option triggered an error. Better to translate the error in something the user can actually recognize as a timeout.
* Diskless replication: set / reset socket send timeout.antirez2014-10-221-0/+2
| | | | | | We need to avoid that a child -> slaves transfer can continue forever. We use the same timeout used as global replication timeout, which is documented to also affect I/O operations during bulk transfers.
* anet.c: new API anetSendTimeout().antirez2014-10-222-0/+16
|
* Diskless replication: less debugging printfs around.antirez2014-10-171-1/+0
|
* rio.c fdset write() method fixed: wrong type for return value.antirez2014-10-171-1/+1
|
* rio fdset target: handle short writes.antirez2014-10-173-2/+18
| | | | | While the socket is set in blocking mode, we still can get short writes writing to a socket.
* anet.c: API to set sockets back to blocking mode.antirez2014-10-172-4/+18
|
* Diskless replication: rio fdset target new supports buffering.antirez2014-10-173-1/+56
| | | | | | | | | | | | | | To perform a socket write() for each RDB rio API write call was extremely unefficient, so now rio has minimal buffering capabilities. Writes are accumulated into a buffer and only when a given limit is reacehd are actually wrote to the N slaves FDs. Trivia: rio lacked support for buffering since our targets were: 1) Memory buffers. 2) C standard I/O. Both were buffered already.
* Diskless replication: Various fixes to backgroundSaveDoneHandlerSocket()antirez2014-10-171-4/+8
|
* Diskless replication: don't send "\n" pings to slaves.antirez2014-10-171-1/+3
| | | | | | This is useful for normal replication in order to refresh the slave when we are persisting on disk, but for diskless replication the child is already receiving data while in WAIT_BGSAVE_END state.
* Diskless replication: remove 40 bytes EOF mark from end of RDB file.antirez2014-10-171-0/+10
|
* Diskless replication: swap inverted branches to compute read len.antirez2014-10-171-2/+2
|
* Diskless replication: don't enter the read-payload branch forever.antirez2014-10-171-0/+3
|
* syncReadLine(): actually enforce buffer size limits.antirez2014-10-161-0/+1
|
* Diskless replication: EOF:<mark> streaming support slave side.antirez2014-10-161-7/+60
|
* Diskless replication: redis.conf and CONFIG SET/GET support.antirez2014-10-164-5/+18
|
* Diskless replication: trigger a BGSAVE after a config change.antirez2014-10-161-12/+17
| | | | | | | | | If we turn from diskless to disk-based replication via CONFIG SET, we need a way to start a BGSAVE if there are slaves alerady waiting for a BGSAVE to start. Normally with disk-based replication we do it as soon as the previous child exits, but when there is a configuration change via CONFIG SET, we may have slaves in WAIT_BGSAVE_START state without an RDB background process currently active.
* Diskless replication flag renamed repl_diskless -> repl_diskless_sync.antirez2014-10-163-9/+9
|
* Diskless replication: trigger diskless RDB transfer if needed.antirez2014-10-162-2/+37
|
* Diskless replication: handle putting the slave online.antirez2014-10-151-31/+57
|
* Diskless replication: read report from child.antirez2014-10-151-15/+57
|
* Diskless replication: child writes report to parent.antirez2014-10-151-0/+40
|
* rio.c fdset target: tolerate (and report) a subset of FDs in error.antirez2014-10-142-3/+22
| | | | | | | | | | | | Fdset target is used when we want to write an RDB file directly to slave's sockets. In this setup as long as there is a single slave that is still receiving our payload, we want to continue sennding instead of aborting. However rio calls should abort of no FD is ok. Also we want the errors reported so that we can signal the parent who is ok and who is broken, so there is a new set integers with the state of each fd. Zero is ok, non-zero is the errno of the failure, if avaialble, or a generic EIO.
* Diskless replication: parent-child pipe and a few TODOs.antirez2014-10-142-4/+35
|
* Diskless replication: RDB -> slaves transfer draft implementation.antirez2014-10-145-28/+200
|
* rio.c: draft implementation of fdset target implemented.antirez2014-10-102-0/+69
|
* rio.c refactoring before adding a new target.antirez2014-10-101-17/+24
|
* Add some comments in syncCommand() to clarify RDB target.antirez2014-10-101-4/+9
|
* Define different types of RDB childs.antirez2014-10-083-0/+9
| | | | | | | | We need to remember what is the saving strategy of the current RDB child process, since the configuration may be modified at runtime via CONFIG SET and still we'll need to understand, when the child exists, what to do and for what goal the process was initiated: to create an RDB file on disk or to write stuff directly to slave's sockets.
* RDB file creation refactored to target non-disk target.antirez2014-10-071-27/+46
|
* Cluster: nodes.conf added to git ignore list.antirez2014-10-071-0/+1
|
* Cluster: more chatty slaves when failover is stalled.antirez2014-10-072-4/+94
|
* Linenoise README updated to match source code.antirez2014-10-061-3/+4
|
* Merge pull request #1902 from mattsta/comment-fixesSalvatore Sanfilippo2014-10-0644-165/+210
|\ | | | | ALL comment fixes
| * redis.conf small grammar fixMiguel Parramon2014-09-291-1/+1
| | | | | | | | | | | | :smile: Closes #2034
| * Fix typoEzequiel Lovelle2014-09-291-1/+1
| | | | | | | | Closes #2029
| * Fix typo in unit testAniruddh Chaturvedi2014-09-291-2/+2
| | | | | | | | Closes #2005
| * Fix typos in commentsGregory Petrosyan2014-09-291-3/+3
| | | | | | | | Closes #2002
| * Add missing 'by'Matt Stancliff2014-09-291-1/+1
| |
View Lorry Controller Status