Agent log limitation to 1MB - is it still valid?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Agent log limitation to 1MB - is it still valid?

kpiwko
Hi All,

in my tests I'm logging invalid requests to the log, which can easily exceed 1MB limit mentioned here http://www.cubrid.org/wiki_ngrinder/entry/how-to-adjust-logger-level during few hours (I haven't reached this limit yet, but I'm pretty close with 900kB per thread). Before creating an issue to make it configurable, I was looking into ngrinder (and grinder) code, but I was not able to find the place where is this limitation enforced.

The only thing I've found was a rolling logger setup for agent.log file.

Isn't that documentation some leftover from previous version? If not, where is this enforced?

Thanks,

Karel
Reply | Threaded
Open this post in threaded view
|

RE: Agent log limitation to 1MB - is it still valid?

junoyoon
Administrator

This limitation comes from logback-worker.xml  file in grinder-3.9.1-patch.jar file in the agent)

You can open it there and modify the xml and repackage it.

However.. it's not the generally recommended approach.

In the large ngrinder deployment.. in which ngrinder is used with more than 1000 people(like we do), we can not expect what will happen in ngrinder.

We found some guys generate more than 10G log files per one test.. They didn't know what they're doing.

At that time, their scripts went wrong.. and each agent emits huge size of exception stacktrace logs..

Then.. these files was transferred to the controller from agents.. which means.. disaster to ngrinder controller and network as well.

The policies which nGrinder contains has been elaborated in our company very long time.

  

  

-----Original Message-----
From: "kpiwko [via ngrinder]"<[hidden email]>
To: "junoyoon"<[hidden email]>;
Cc:
Sent: 2013-09-13 (금) 17:24:42
Subject: Agent log limitation to 1MB - is it still valid?

Hi All,

in my tests I'm logging invalid requests to the log, which can easily exceed 1MB limit mentioned here http://www.cubrid.org/wiki_ngrinder/entry/how-to-adjust-logger-level during few hours (I haven't reached this limit yet, but I'm pretty close with 900kB per thread). Before creating an issue to make it configurable, I was looking into ngrinder (and grinder) code, but I was not able to find the place where is this limitation enforced.

The only thing I've found was a rolling logger setup for agent.log file.

Isn't that documentation some leftover from previous version? If not, where is this enforced?

Thanks,

Karel



If you reply to this email, your message will be added to the discussion below:
http://ngrinder.642.n7.nabble.com/Agent-log-limitation-to-1MB-is-it-still-valid-tp898.html
To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

RE: Agent log limitation to 1MB - is it still valid?

kpiwko
Awesome, that's exactly what I need. Thanks JunHo!

Just a note, I do not expect to generate such huge logs, it's rather about possibility to override it in cases when it becomes necessary.
Reply | Threaded
Open this post in threaded view
|

RE: Agent log limitation to 1MB - is it still valid?

junoyoon
Administrator
I'm just telling you why I have to limit log size. :-)