Anyone come across an overly large ra_ent_processlogrecord table in the Server repository?
Hi all,
I noticed that one of our installations of RapidMiner Server 7.x had a repository size of 5 Gigs. When looking deeper I found that 4.8GB of the 5GB was in the table ra_ent_processlogrecord. Has anyone come across this table getting overly large or do I just have an excitable database server?
Best Answers
-
No need, it needs an update to RM Server 8 soon anyway. I've tracked it down to a process error that appears to have looped entries in this log repeatedly. (Several million of them :mansurprised: ).
No big worry, I know that I can safely clear that table without breaking anything. I'll just setup a stored procedure to make sure the table doesn't grow too big in future.
2 -
Hi all,
well, over the time this log table grows and grows...however, as far as I remember, there's a setting for the server limiting the maximum size by discarding old entries.
Unfortunately I don't remember the name...something like max_log_entries or similar...
Greetings,
Sebastian
0
Answers
-
John,
have a chat with Helge on our official support. I vaguely remember that he ran into such a case a year ago...
Cheers,
Martin
1 -
No need, it needs an update to RM Server 8 soon anyway. I've tracked it down to a process error that appears to have looped entries in this log repeatedly. (Several million of them :mansurprised: ).
No big worry, I know that I can safely clear that table without breaking anything. I'll just setup a stored procedure to make sure the table doesn't grow too big in future.
2 -
Hi all,
well, over the time this log table grows and grows...however, as far as I remember, there's a setting for the server limiting the maximum size by discarding old entries.
Unfortunately I don't remember the name...something like max_log_entries or similar...
Greetings,
Sebastian
0