Skip to content

Conversation

@abhinigam
Copy link

There are a bunch of changes here:

  1. Added metrics to track the number of active threads/current threads in server thread pool.
  2. Added metrics in JMX to track in microseconds the total response time including the queue time, the queue time.
    Fixed an issue where we seem to be overwriting times in some exception handlers.
  3. If a request were to take longer than the stale request timeout amount we will just log where the request originated from instead of dumping the entire message into a log. This causes a bad situation to become worse.
  4. Currently the requestTimeoutMillis only checks time before a thread from the thread pool picks up request from the queue. It does not re-check this after the response handler is done executing the request. I have added a new parameter reponseGenerationTimeoutMillis for this precise reason. To preserve backward compatibility this is set as -1. Ideally if you want the fixed behavior you should probably set it to be the same as requestTimeoutMillis.
  5. For backward compatibility I have left the original metric AverageRequestProcessing timetracker as is. Instead I have created two new ones for tracking queue time and total response processing times.

Dmytro Ivchenko and others added 30 commits June 28, 2013 12:39
FIX: change version back to 0.6.33
Fixed some norbert tuning parameters to take into account milliseconds to microseconds
Updating Netty Version in Norbert for USCP 2050
@apurvam apurvam deleted the FixBugs branch December 12, 2013 01:54
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.

6 participants