Skip to content

Fix #766: Remove recrawl startup API entry on stop - #767

Open
pr0vieh wants to merge 3 commits into
yacy:masterfrom
pr0vieh:fix/766-recrawl-stop-cleanup-masterbase
Open

Fix #766: Remove recrawl startup API entry on stop#767
pr0vieh wants to merge 3 commits into
yacy:masterfrom
pr0vieh:fix/766-recrawl-stop-cleanup-masterbase

Conversation

@pr0vieh

@pr0vieh pr0vieh commented Feb 27, 2026

Copy link
Copy Markdown
Contributor

sry for delay
i'm currently working on remove this RWI blob stuff vom yacy using RocksDB implementation

Description

This PR fixes #766, where a previously stopped recrawl job could restart again after peer reboot.

What changed

On recrawl start, the PR stores the primary key (PK) of the created startup API entry in config [recrawlindex.startup.apicall.pk].
On Stop, it deletes exactly that tracked API entry (targeted deletion), instead of clearing all matching recrawl entries.

Why

Prevents unwanted recrawl auto-restart after a user explicitly stopped the job.
Avoids accumulating stale startup entries in the API table.
Preserves existing report visibility after termination.

@okybaca

okybaca commented Mar 31, 2026

Copy link
Copy Markdown
Contributor

thanks for that <3, @pr0vieh, and sorry for silence, the spring started and is hard to stay in front of computer ;0
will test that soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Recrawler job starts after restart even when terminated before

2 participants