Created input stats endpoint

[adamschmidt]

Added server monitoring for input stats and an HTTP endpoint alongside the existing health check and sink stats.

[cloudbees-pull-request-builder]

suro-pull-requests #192 FAILURE
Looks like there's a problem with this pull request

[cloudbees-pull-request-builder]

NetflixOSS » suro » suro-pull-requests #23 ABORTED

[cloudbees-pull-request-builder]

suro-pull-requests #193 FAILURE
Looks like there's a problem with this pull request

[cloudbees-pull-request-builder]

NetflixOSS » suro » suro-pull-requests #24 FAILURE
Looks like there's a problem with this pull request

[adamschmidt]

Anything I need to do for this, or is it another stuck build?

[metacret]

Hi Adam

Could you take a look at
https://netflixoss.ci.cloudbees.com/job/NetflixOSS/job/suro/job/suro-pull-requests/24/console
?

This build is not stuck, just compileTestJava failed.

Thank you
Best, Jae

On Tue, Feb 24, 2015 at 3:06 AM, adamschmidt [email protected]
wrote:

Anything I need to do for this, or is it another stuck build?

—
Reply to this email directly or view it on GitHub
#201 (comment).

[cloudbees-pull-request-builder]

NetflixOSS » suro » suro-pull-requests #31 FAILURE
Looks like there's a problem with this pull request

[cloudbees-pull-request-builder]

suro-pull-requests #201 FAILURE
Looks like there's a problem with this pull request

[cloudbees-pull-request-builder]

suro-pull-requests #202 FAILURE
Looks like there's a problem with this pull request

[cloudbees-pull-request-builder]

NetflixOSS » suro » suro-pull-requests #32 ABORTED

[adamschmidt]

I've fixed the broken code, but there seems to be an unrelated problem with the test execution timing out at 20 mins.

[metacret]

I will take a look.

On Tue, Feb 24, 2015 at 4:47 PM, adamschmidt [email protected]
wrote:

I've fixed the broken code, but there seems to be an unrelated problem
with the test execution timing out at 20 mins.

—
Reply to this email directly or view it on GitHub
#201 (comment).

[metacret]

@adamschmidt Sorry for late response. If you take a look at this, I can see the following error messages on running unit tests

15/02/24 16:10:21 ERROR thrift.MessageSetProcessor: Exception when processing message set null
java.lang.NullPointerException
    at com.netflix.suro.input.thrift.MessageSetProcessor.process(MessageSetProcessor.java:174)
    at com.netflix.suro.input.thrift.TestMessageSetProcessor.testQueue(TestMessageSetProcessor.java:79)
    at com.netflix.suro.input.thrift.TestMessageSetProcessor.testFileQueue(TestMessageSetProcessor.java:60)

Could you take a look at this? TestMessageSetProcessor unit test should be passed.