Query Suggestion Options
Last word completion
Keyboard Layouts
GitHub

👀 While it's loading, feel free to check out the other repositories:

🔔 To get a notification when it's ready, leave your email here:

By entering your email, you agree to receive notifications and marketing-related emails

Filter by reset

175 results 12 ms in manticoresoftware/manticoresearch-backup

typos, use str_contains/is_writable and static usage for static methods

sorry for one path for all changes, but its simple

GemorrojGemorroj · 2023-02-23 · 1 · #53

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

could you upload your backup of the products index that we could try to restore and investigate the hung? You could upload your data as explained in the manual

tomatologtomatolog · 2024-06-06

Store config name in meta file on backup and use it on restore

Currently, we are only storing versions when we perform a backup. However, there is an issue with hardcoded values that we should aim to remove: https://github.com/manticoresoftware/manticoresearch-backup/blob/fa1fecdf149e60248b47e1acfe64cf23d9c83fee/src/ …

donhardmandonhardman · 2024-07-02 · 1 · #117

enhancementest::size_S

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Uploaded a backup of the product index: issue-116.

srgtestsrgtest · 2024-06-07

Backup plain indexes

While it may not make much practical sense to backup plain indexes since they are mostly immutable we can still do it to: make things unified backup updated attributes make things easier for those who find it easier to run backup/restore than rsync/cp

sanikolaevsanikolaev · 2023-01-13 · 0 · #48

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Any information on the problem?

srgtestsrgtest · 2024-06-14

Add support for external storages

It will makes things easier if we support backing up directly to an external storage like ssh and s3. Here's what the syntax may look like in SQL: BACKUP [<what>] TO <where> [OPTIONS <options>] <where> should in the form of a function : local({path=}) or …

sanikolaevsanikolaev · 2023-01-04 · 0 · #47

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Looks like more tables or additional load are required to reproduce the issue: snikolaev@dev2:~/issue-116$ manticore-backup --config=manti.conf --backup-dir=backup Copyright (c) 2023-2024, Manticore Software LTD (https://manticoresearch.com) Manticore …

sanikolaevsanikolaev · 2024-06-14

can't restore when another searchd is running

I can't restore an instance when another searchd instance is running: root@perf ~/repl/1 # cat manticore1.conf searchd { listen = 127.0.0.1:20308:http listen = 127.0.0.1:20201 listen = 127.0.0.1:20301:mysql log = searchd.log query_log = query.log pid_file …

sanikolaevsanikolaev · 2023-03-28 · 0 · #63

bug

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Yes, without load there are no problems. But when you remove a backup to the product index, there are SELECT and UPDATE . There is an idea that this is due to load and requests. At this moment, the backup is FREEZE before the backup is completed, and …

srgtestsrgtest · 2024-06-17

Can't restore when the config file name is custom

Can't restore when the config file name is custom: root@perf ~/repl/1 # manticore-backup --backup-dir=/root/repl/1/backup --restore=backup-20230328051059 Copyright (c) 2023, Manticore Software LTD (https://manticoresearch.com) Manticore config file: …

sanikolaevsanikolaev · 2023-03-28 · 0 · #64

bug

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Pls let me know what update and select queries are running during backup. Simple: snikolaev@dev2:~$ while true; do mysql -P9315 -h0 -e "update products set nds=21 where id=612731;update products set nds=20 where id=612731"; echo -n .; done; doesn't change …

sanikolaevsanikolaev · 2024-06-18

Restore particular tables

It would be great to be able to restore a particular table. IMPORT can be automated for that, e.g.: root@bb5278967f62:/# mysql -P9306 -h0 -e "insert into t(f) values('abc'); flush ramchunk t;" root@bb5278967f62:/# mysql -P9306 -h0 -e "insert into t2(f) …

sanikolaevsanikolaev · 2024-01-19 · 0 · #58

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

There is a query.log log for this date. In the attachment, there are queries that were executed during the backup period. query.log.2.gz Can be compared by time.

srgtestsrgtest · 2024-06-18

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

from query.log you provided I see the last queries were /* Wed Jun 05 06:53:18.396 2024 conn 14060 (10.9.2.195:51636) real 0.522 wall 0.523 found 1190452 */ SELECT id, then there is a gap and next queries with errors seems come after daemon restart ... /* …

tomatologtomatolog · 2024-06-18

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

When the daemon froze, the requests were no longer received and were not recorded in the logs. I can also attach log files, you can see the time there.

srgtestsrgtest · 2024-06-19

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

@srgtest what may work out is if you just give us a few typical queries you make and some info about the load like: one update per second like this ... 2 selects per second like this ...

sanikolaevsanikolaev · 2024-06-19

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

@sanikolaev Ok, I'll try to collect such information and requests.

srgtestsrgtest · 2024-06-21

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

I have the same problem. A backup on a loaded database fails with an error and work is blocked. root@ec2733c78e2d:/tmp# manticore-backup --backup-dir=/tmp Copyright (c) 2023-2024, Manticore Software LTD (https://manticoresearch.com) Manticore config file: …

nxjtsnxjts · 2024-07-08

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Average load ~ 2000 requests. Usually there are more updates, but there are also selections. 2000 requests per second, mostly updates?

sanikolaevsanikolaev · 2024-07-09

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

I've reproduced smth similar when backing up a few gigabytes table under heavy UPDATE load: 2024-07-09 04:48:02 [Info] name... Fatal error: Uncaught Manticoresearch\Backup\Exception\SearchdException: Failed to send query to the Manticore Search daemon. …

sanikolaevsanikolaev · 2024-07-09

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

@srgtest @nxjts Can you confirm you were updating a string/json attribute when it hanged? Here's what I've reproduced: MRE Config: snikolaev@dev2:~$ cat 116.conf searchd { listen = 9315:mysql listen = 9316 log = searchd.log pid_file = searchd.pid data_dir …

sanikolaevsanikolaev · 2024-07-09

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Most often uint, bigint, mva. Less often json.

nxjtsnxjts · 2024-07-09

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

Can be still reproduced in a newer version: Manticore 6.3.7 640fac840@24092910 dev (columnar 2.3.1 f9ef8b9@24090411) (secondary 2.3.1 f9ef8b9@24090411) (knn 2.3.1 f9ef8b9@24090411)

sanikolaevsanikolaev · 2024-09-30

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

actually it is not necessary to 'bomb' instance with updates. Just 3 steps (over existing table): freeze t; update ...; (once) unfreeze t; (from another connection) perfectly make a deadlock

klirichekklirichek · 2024-10-18

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

fix provided in rev. 9987798a (of the manticore project)

klirichekklirichek · 2024-10-18

manticore-backup Failed to send query to the Manticore Search daemon

srgtestsrgtest · 2024-11-01 · 24 · #116

bugest::size_Mrel::upcoming

fix provided in rev. 9987798a (of the manticore project) Here's the link - https://github.com/manticoresoftware/manticoresearch/commit/9987798a

sanikolaevsanikolaev · 2024-10-18