Skip to content
Snippets Groups Projects
  1. Oct 18, 2013
  2. Oct 13, 2013
    • Konstantin Osipov's avatar
      Remove palloc. Use region_alloc instead. · b01d75b1
      Konstantin Osipov authored
      Instead of palloc allocator use a member of small allocators family,
      region_alloc.
      
      The plan is to remove salloc as well, and switch entire tarantool
      to libsmall.
      
      Fix a race condition in replication/swap.test, discovered with the
      new allocator.
      b01d75b1
  3. Oct 12, 2013
  4. Oct 09, 2013
    • Konstantin Osipov's avatar
      https://blueprints.launchpad.net/tarantool/+spec/start-replication-last-dump · c67278ce
      Konstantin Osipov authored
      Review fixes:
      
      - New configuration variable 'replication_protocol'
      is defined in the configuration file. The original patch
      would hand-craft it into generated files.
      - Simplified  numeric version id generation.
      - Removed timeouts from new sio_* calls. They did't quite work,
      especially with blocking sockits. Timeouts should at least use
      select(), which updates wait time on exit..
      - Removed include cfg/tarantool_box_cfg.h into recovery.cc, instead
      passed around all arguments explicitly.
      - Removed unused headers.
      - reused handshake code in master and replica
      - simplified handshake in replica fiber
      - removed clutter
      - touched here and there.
      c67278ce
  5. Oct 04, 2013
  6. Sep 30, 2013
  7. Sep 27, 2013
  8. Sep 26, 2013
  9. Sep 25, 2013
  10. Sep 24, 2013
  11. Sep 23, 2013
  12. Sep 20, 2013
  13. Sep 19, 2013
  14. Sep 18, 2013
  15. Sep 16, 2013
  16. Sep 12, 2013
  17. Sep 10, 2013
  18. Sep 08, 2013
  19. Sep 07, 2013
  20. Sep 03, 2013
    • Konstantin Osipov's avatar
      A hack to fix opentar-42 (mail.ru ticket). · 9a8f78e4
      Konstantin Osipov authored
      What happened in production, during upgrade:
      - logger option in the config file was pointing to nowhere
      - the server would start, unable to check that the child logger
      process died prematurely
      - the server would fork spawner process to spawn replication relays
      - a replica would come in, asking for data
      - the spawner would successfully spawn a relay but die on SIGPIPE
      when trying to write to the log (a pipe leading nowhere by now)
      about the event
      -> we have a master with a dead spawner process, no more replicas,
      sorry.
      
      Well, someone should check their configuraiton in the first place.
      Nevertheless, try to be nice, and:
      
      - don't die on SIGPIPE in the spawner process.
      - when starting the logger, make an effort to check that it has started
      successfully. There is no reliable way to find this out, so do
      it with the best effort.
      9a8f78e4
  21. Aug 31, 2013
  22. Aug 30, 2013
  23. Aug 28, 2013
Loading