Bug 332317 - delay reindexing an already indexed file
Summary: delay reindexing an already indexed file
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords:
: 333954 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-19 11:04 UTC by Martin Koller
Modified: 2019-06-06 19:59 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Koller 2014-03-19 11:04:08 UTC
KDE 4.12.90, openSuse
Today I have baloo_file_extractor more or less always at 100%CPU.
Checking why it does that, I found out that I have konversation (chat IRC client) running, which can not connect to the freenode server due to company firewall - which means konversation writes a lot of error log messages into ~/logs/freenode.log - continuously.

This obviously leads to the problem that baloo again and again tries to index this logfile.

Reproducible: Always



Expected Results:  
The baloo_file_indexer shall be improved to avoid such situation, e.g.:
keep an internal list of files which have been reindexed already two times in the last 5 minutes or so (two times to avoid to have ALL files in this list).
When a file change is detected for a file in this list, do not immediately reindex the file but wait for another 5 minutes.

Timeout should be a sane default, probably let it be configurable in a config file
Comment 1 Vishesh Handa 2014-07-29 16:33:32 UTC
*** Bug 333954 has been marked as a duplicate of this bug. ***
Comment 2 Stefan Brüns 2019-06-06 18:43:12 UTC
So, why do you think this is a problem?
Comment 3 Martin Koller 2019-06-06 18:58:33 UTC
I consider using 100% CPU continuously as a problem.
Comment 4 Stefan Brüns 2019-06-06 19:04:59 UTC
I have a dozen IRC channels open in konversation which are reindexed all the time, but I see no significant CPU load, so your problem is definitely something different.
Comment 5 Martin Koller 2019-06-06 19:08:24 UTC
1) You are testing with KDE 4.12.90, which was the version I originally reported the bug with ?
2) You are also testing in a network which does not reach your IRC servers, as described in my report ?

If 2 but not 1, maybe the bug has been already solved.
Comment 6 Nate Graham 2019-06-06 19:10:28 UTC
I hope you're not still using KDE4. That's deprecated and not receiving any bug fixing activity. Are you able to test with a recent version of KDE Frameworks, or build Baloo from source? A lot has happened in five years. :)
Comment 7 Martin Koller 2019-06-06 19:59:34 UTC
I did not say I'm still using that old KDE4 version (actually baloo5-file-5.45.0, openSuse Leap 15.0).
I just mentioned that a test with a version different to the reported one might not show the problem anymore.

I tried now to simulate the situation by adding data to a text file which I want to index,
and so far I see no problem.
Let's close this report