1. Main development threads

(question) UNDER CONSIDERATION

(grey lightbulb)PLANNED(lightbulb)STARTED(tick)FINISHED

This page presents a status of the ongoing developments

StatusPrioritySummaryJIRA Ticket
(tick)HIGHRefactoring the Configuration service

DM-28860 - Getting issue details... STATUS

(grey lightbulb)HIGHRedesign of Qserv's "Empty Chunk Lists" into "Chunk Inventory"
(grey lightbulb)MEDIUMAdd chunk versioningCreate a ticket (warning)
(tick)CRITICALHuge memory leak in the Master Replication Controller when Qserv workers are down


(grey lightbulb)HIGHIntegration test for the Replication SystemCreate a ticket (warning)
(tick)MEDIUMSecurity reinforced protocol for Controllers/Workers communications and worker database operations
(tick)
Reinforce the controllers / workers  and file client  / file server  protocols to carry over and verify a unique identifier of a Qserv instance, so that the Replication system's configuration errors were properly detected and handled, and cross-talks between two or many instances of the Replication system were prevented.

DM-23191 - Getting issue details... STATUS

(tick)
A Design of the Qserv Monitoring System

DM-13751 - Getting issue details... STATUS

(tick)
Implement Qserv Monitoring Services (the Dashboard)

DM-13752 - Getting issue details... STATUS

(tick)
  • Simple management scripts for running the system in PDAC
  • Setup, configure, tests and deploy for production
  • Fixed-logic master Replication Controller
  • Controller side flow control and optimal worker load for the replication and cluster rebalancing algorithms

DM-14292 - Getting issue details... STATUS DM-16224 - Getting issue details... STATUS

(tick)
Master replication controller with built-in REST API support

DM-10425 - Getting issue details... STATUS

(tick)
Deploying, configuring and operating the Qserv Replication system


(tick)
Improved container build procedure for the Replication System's tools

DM-16790 - Getting issue details... STATUS

(tick)
Migrate binary tools of the Replication system to the common Application framework

DM-17113 - Getting issue details... STATUS

(tick)
Add REST services for monitoring and managing the Replication System

DM-16788 - Getting issue details... STATUS

(tick)

Evaluate Ingest Improvement Requirements for Qserv

DM-17655 - Getting issue details... STATUS

(tick)
Minor code refactoring

DM-18401 - Getting issue details... STATUS

(tick)
Evaluate MySQL table partitioning for the reliable ingest with the rollback optionNo ticket required for this effort. All details are found within a document linked on this row.
(tick)
Worker database management

DM-17812 - Getting issue details... STATUS

worker service needs to connect directly to the MariaDB service of the Qserv worker

(tick)
Implement a framework for sampling monitoring parameters of Qserv workers

DM-19226 - Getting issue details... STATUS

(tick)
Add support for super-transactions

DM-19156 - Getting issue details... STATUS

(tick)
Integrate Qserv replication system with CSS

DM-18004 - Getting issue details... STATUS

Master Replication Controller needs to connect directly to the MariaDB service of the Qserv master

(tick)
Log REST requests to the Master Replication Controller into the Event LogThis was implemented as a refactoring stage of the Replication system's code before a work on the new Ingest system began.
(tick)
Improve tracking of the asynchronous operations (jobs/requests)

DM-18743 - Getting issue details... STATUS

(tick)
Garbage collection at Replication workers

DM-22428 - Getting issue details... STATUS

2. General code improvements, refactoring, cleanup

(question) UNDER CONSIDERATION

(grey lightbulb)PLANNED(lightbulb)STARTED(tick)FINISHED

These projects have generally low priority, and they're meant to improve the overall quality and robustness of the code, as well as make it more maintainable in the long run.

StatusPrioritySummaryJIRA Ticket
(grey lightbulb)MEDIUMImproved version number handling in the REST APICreate a ticket (warning)
(grey lightbulb)MEDIUMTesting framework for the REST APICreate a ticket (warning)
(grey lightbulb)LOW

Fix incomplete implementation of the method:

json HttpConfigurationModule::_addTable() {
    debug(__func__);

    // FIXME: extend the service to accept all attributes of the table.
    // Create a method in the base class to extract standard attributes from
    // from the requests's body. Use this method here and in the method HttpIngestModule::_addTable


(grey lightbulb)LOWFix incorrect naming convention for the object identifiers in the director and dependent tables
(lightbulb)LOWEliminate Doxygen style comments from the codeNo ticket is required
(tick)LOWAllow protobuf dependencies in the worker-side replication requestsPartially implemented for a family of  SQL requests when implementing a new Ingest system. More work is needed for other types of worker-side requests.
(grey lightbulb)LOWMigrate to using std::chrono in the public API of the Replication Framework
(question)LOWMore robust implementation of the asynchronous handlers
(tick)LOW Refactor operations with chunked table names to class ChunkedTable 
(question)LOWCode refactoring in the asynchronous event handlers of Requests and Jobs
(question)LOWStyle refactoring in the range-based for loops
(tick)
Optimized implementation of class SqlRemoveTablePartitionsJob

DM-22135 - Getting issue details... STATUS

(tick)
Refactor the HTTP Processor of the Master Replication Controller

DM-21803 - Getting issue details... STATUS

(tick)
Refactor results reporting in the implementation of class ControllerApp

DM-21524 - Getting issue details... STATUS

3. Known bugs, outstanding issues, etc.





  • No labels