Skip to content
Snippets Groups Projects
  1. Sep 23, 2016
  2. Sep 22, 2016
  3. Sep 21, 2016
  4. Sep 20, 2016
    • Roman Tsisyk's avatar
      vinyl: follow up box.cfg.vinyl.threads = 1 · 2f4a1c5d
      Roman Tsisyk authored
      2f4a1c5d
    • Roman Tsisyk's avatar
      vinyl: refactor vy_run_iterator_load_page · c5b3b4c4
      Roman Tsisyk authored
      * Merge vy_run_read_page to vy_run_iterator_load_page
      * Move struct vy_page code to struct vy_run_iterator section
      
      Needed for #1756
      c5b3b4c4
    • Roman Tsisyk's avatar
      vinyl: start only one worker thread by default · 1f58bc7f
      Roman Tsisyk authored
      Change default value of box.cfg.vinyl.threads to 1.
      Keep 3 workers in the test suite.
      1f58bc7f
    • Roman Tsisyk's avatar
      vinyl: disable scheduler during recovery · e128864d
      Roman Tsisyk authored
      e128864d
    • Roman Tsisyk's avatar
      vinyl: remove fixed timeout from scheduler · d793f06e
      Roman Tsisyk authored
      Wake up scheduler if range dump conditions are met.
      
      Fixes #1769
      d793f06e
    • Roman Tsisyk's avatar
      Process initial replication join in TX thread · dba97493
      Roman Tsisyk authored
      Refactor replication relay to invoke Engine::join() using TX thread.
      Now engines can start their own threads when needed:
      
      * MemTX starts a new cord to read rows from a snapshot file.
      * Vinyl should use coeio for disk operations (see #1756).
      
      This patch fixes race conditions between relay and TX threads
      for both engines.
      
      Closes #1757
      dba97493
    • Vladimir Davydov's avatar
      vinyl: cleanup range file creation · a46865db
      Vladimir Davydov authored
       1. Consolidate temp file creation, initial run write, and range file
          rename in a single function, vy_range_write_run(). Use it in both
          dump and compact procedures.
      
       2. Do unlink on range file write failure in vy_range_write_run()
          instead of postponing it unilt vy_range_delete().
      
       3. #2 allows us to move range->id initialization from
          vy_range_complete() to vy_range_new(), as uninitialized ->id was
          only used to check if a range file is incomplete and delete it in
          vy_range_delete().
      
       4. #3 allows to make index->range_id_max non-atomic, as vy_range_new()
          is only called from the tx thread (in contrast to vy_range_complete,
          which hosted range->id allocation before).
      a46865db
  5. Sep 19, 2016
Loading