[SON-HIVE Voting] Refactor sidechain plugin to use separate son schedulers per sidechain

serkixenos commented

2022-03-03 19:15:01 +00:00

(Migrated from gitlab.com)

The goal is to separate voting for Bitcoin and Hive SONs, so that they can act independently of each others.
All code affected by this change should be refactored, in a way that enables that Bitcoin SON and Hive SON are considered separate entities.

The function of interest is

void peerplays_sidechain_plugin_impl::son_processing()

Since we will be using separate schedulers, processing BTC/Hive/HBD might happen in parallel, not like now, in serial manner.

Simplified, we can start separate "per sidechain" processing threads from here

void peerplays_sidechain_plugin_impl::schedule_son_processing() {
   fc::time_point now = fc::time_point::now();
   int64_t time_to_next_son_processing = 500000;

   fc::time_point next_wakeup(now + fc::microseconds(time_to_next_son_processing));

   _son_processing_task = fc::schedule([this] {
      son_processing();
   },
                                       next_wakeup, "SON Processing");
}

The goal is to separate voting for Bitcoin and Hive SONs, so that they can act independently of each others. All code affected by this change should be refactored, in a way that enables that Bitcoin SON and Hive SON are considered separate entities. The function of interest is ``` void peerplays_sidechain_plugin_impl::son_processing() ``` Since we will be using separate schedulers, processing BTC/Hive/HBD might happen in parallel, not like now, in serial manner. Simplified, we can start separate "per sidechain" processing threads from here ``` void peerplays_sidechain_plugin_impl::schedule_son_processing() { fc::time_point now = fc::time_point::now(); int64_t time_to_next_son_processing = 500000; fc::time_point next_wakeup(now + fc::microseconds(time_to_next_son_processing)); _son_processing_task = fc::schedule([this] { son_processing(); }, next_wakeup, "SON Processing"); } ```

serkixenos commented

2022-03-03 19:15:33 +00:00

(Migrated from gitlab.com)

changed title from Refactor sidechain plugin to use son schedulers to Refactor sidechain plugin to use {+separate +}son schedulers{+ per sidechain+}

changed title from **Refactor sidechain plugin to use son schedulers** to **Refactor sidechain plugin to use {+separate +}son schedulers{+ per sidechain+}**

serkixenos commented

2022-03-03 19:57:56 +00:00

(Migrated from gitlab.com)

These functions, from peerplays_sidechain_plugin should be refactored to their "per sidechain" variants

   std::set<chain::son_id_type> &get_sons();
   const son_id_type get_current_son_id();
   const son_object get_current_son_object();

These functions, from peerplays_sidechain_plugin should be refactored to their "per sidechain" variants ``` std::set<chain::son_id_type> &get_sons(); const son_id_type get_current_son_id(); const son_object get_current_son_object(); ```

hbelakon commented

2022-03-08 03:53:57 +00:00

(Migrated from gitlab.com)

changed title from Refactor sidechain plugin to use separate son schedulers per sidechain to {+[SON-HIVE Voting] +}Refactor sidechain plugin to use separate son schedulers per sidechain

changed title from **Refactor sidechain plugin to use separate son schedulers per sidechain** to **{+[SON-HIVE Voting] +}Refactor sidechain plugin to use separate son schedulers per sidechain**

hbelakon commented

2022-03-08 03:54:09 +00:00

(Migrated from gitlab.com)

assigned to @serkixenos

hbelakon commented

2022-03-08 03:54:54 +00:00

(Migrated from gitlab.com)

@serkixenos please estimate

serkixenos commented

2022-03-09 03:02:30 +00:00

(Migrated from gitlab.com)

Base your work on feature/son-for-hive-voting branch