Move vshard related fields from _pico_property to _pico_tier
and adapt it in governor algorithm

Kurdakov Alexander authored 8 months ago and Alexander Kurdakov committed 8 months ago

Creating default tier on absence of `tier` section in configuration file
taking into account `default_replication_factor`.

default tier persisted only in the absence of configuration file

This partially reverts commit 6f0cee63.

Kurdakov Alexander authored 9 months ago and Alexander Kurdakov committed 9 months ago

following sections were renamed:
tiers -> tier
peers -> peer

Georgy Moshkin authored 10 months ago and Dmitry Rodionov committed 9 months ago

Previously tests did change environment variables and since they run in
parallel this lead to other tests failing because of unexpected env
content

Co-authored-by: Dmitry Rodionov <d.rodionov@picodata.io>

this fixes the following bug:
```
picodata run --data-dir tmp/i1/
C> invalid socket path: tmp/i1//admin.sock
[supervisor:214288] no ipc message from child
[supervisor:214288] subprocess 214289 exited with code 1
```

Currently only 2 cases are supported:
- config_file
- commandline_or_environment

godzie44 authored 1 year ago and Yaroslav Dynnikov committed 11 months ago

Introduce a plugin system for picodata cluster.
Plugin system contains:
- `picoplugin` crate with plugin interfaces.
This crate exposes plugin interfaces for user implementation and API
that used by picodata to interact with plugin as with a code from dynamic library.
- Support for plugin work cycle in picodata instance work cycle.
Picodata instance interacts with running plugin by `PluginManager`
component.
Typically, plugins react to events that occur in instance or whole cluster.
- New lua API with plugin CRUD actions.
    - pico.create_plugin - load a new plugin into picodata cluster
    - pico.remove_plugin - remove plugin from picodata cluster
    - pico.update_plugin_config - update plugin service configuration

We don't expect users to be changing those too often.