Calling the logger 'main' may cause confusion to external readers not familiar
with the source code, since there is nothing 'main' about this logger in
particular - that is just the file name.
It is then called the start up log.
Signed-off-by: Glauber Costa <glommer@cloudius-systems.com>
* seastar beeaccb...3cf6bee (4):
> dpdk: i40e_should_linearize(): Check the resulting cluster and not the original packet
> reactor: fix inverted logic in recursive_touch_directory()
> build: suport -march=... in cflags
> tests: futures_test: Add test case for parallel_for_each()
The same way we create a directory for the sstables, we should do it for the
commitlog.
If you, like me, have been using the --datadir directive, the fact that we
don't do it would have slipped away: when using --datadir, both the commitlog
and sstables will be put in this same root.
However, when using the system defaults from the configuration file, this won't
be true.
Signed-off-by: Glauber Costa <glommer@cloudius-systems.com>
There is a small but potentially serious mistake in the way we are computing
the number of regular columns. We are using an incorrect offset, and the
number of regular columns in a table like this:
schema(...,
{{"pk", utf8_type}},
{{"ck", utf8_type}, {"ck2", utf8_type}},
{
{"reg1", long_type},
{"reg2", long_type},
},
{{"static", utf8_type}},
utf8_type,
"comment"
);
is being reported as 3.
Fix this
Signed-off-by: Glauber Costa <glommer@cloudius-systems.com>
We should only call column_family::start after the checks because
if a check failed, column_family would be destroyed without
column_family::stop being called first, and that would lead to
a problem, such as _compaction_done future not being resolved.
Signed-off-by: Raphael S. Carvalho <raphaelsc@cloudius-systems.com>
Our main has a "on_terminate()" to make sure it exits when there is an
exception during initialization, instead of hanging. But it's in the
wrong place - it needs to be on the outer future.
Before this patch, an error parsing the command line will result in
a "WARNING: exceptional future ignored ..." and a hang, instead of a
"Exiting on unhandled exception..." and an exit as we get after this
patch.
Signed-off-by: Nadav Har'El <nyh@cloudius-systems.com>
* seastar 732dba1...beeaccb (4):
> future: fix parallel_for_each returning to quickly on error
> tests: add test case for parallel_for_each early return on error
> net::dpdk::i40e_should_linearize(): Don't assume that all headers are in frag0
> net::dpdk: rename max_non_tso_i40e_frags
Handling row marker expiry from Pawel:
This series fixes row expiration. Row markers are used to make sure that
row exists even if it has no cells and therefore they also need to be
expired properly. Origin gets that for free since in their architecture
row marker is a normal cell. We use different approach with deletable_row
storing marker information and therefore additional logic must be added
to make sure that expiration works correctly.
INSERT statements update row marker ttl and expiry to the same values
which are set to the added/modified cells.
Signed-off-by: Paweł Dziepak <pdziepak@cloudius-systems.com>
Row marker can be in one of three states: missing, live (possibly
expiring) or dead. Since it basically behaves like a normal cell, except
it doesn't have any value, row_marker class provides an interface
similar to atomic_cell.
Signed-off-by: Paweł Dziepak <pdziepak@cloudius-systems.com>
