1
0
mirror of https://github.com/mariadb-corporation/mariadb-columnstore-engine.git synced 2025-07-30 19:23:07 +03:00
Commit Graph

10 Commits

Author SHA1 Message Date
9ef5d7f3ac fix(SM): check for duplicates (#3316)
Co-authored-by: Roman Nozdrin <rnozdrin@mariadb.com>
2024-09-10 17:51:35 +03:00
4fe9cd64a3 Revert "No boost condition (#2822)" (#2828)
This reverts commit f916e64927.
2023-04-22 15:49:50 +03:00
f916e64927 No boost condition (#2822)
This patch replaces boost primitives with stdlib counterparts.
2023-04-22 00:42:45 +03:00
04752ec546 clang format apply 2022-01-21 16:43:49 +00:00
cd5e872104 Removed unnecessary debugging printouts/logging, fixed a couple add'l bugs. 2020-05-27 16:37:51 -04:00
c29050899d Took out the cache repopulate idea. Now we will only have warnings
of problems.

I realized we can't reliably tell how big the cache is while the system
is running.  There's a window where write/append has added / is adding
a journal file but hasn't told Cache about it yet.  This capability will
have to wait for now.

This shouldn't be a problem because in theory, we will no longer have
data whose size is not consistent with metadata stored outside of the file.
If we do, it means there was either a hard failure, or SM was killed.
Either way, SM will be restarted and the cache will populate its meta
fresh then.
2020-05-27 16:36:18 -04:00
aeec468814 Fixed a number of bugs in storage manager, and added code to detect
and recover from being killed while writing new objects.

Conflicts:
	storage-manager/src/Synchronizer.cpp
2020-05-27 16:36:08 -04:00
044ed75176 left out %s in logging message 2019-10-17 15:02:33 -05:00
ab614da63c MCOL-3499: WriteTask failure was sending 2 responses and fix race between prefixCache::populate and writing new S3 objects. 2019-10-17 14:25:28 -05:00
fba0c1728c Relocating everything in the repo s.t. it can be merged into
the columnstore repo.
2019-08-14 11:07:24 -05:00