Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question
0

Slow consumer - trigger

Is there some Mechanism to find who is a slow consumer on a space? Atleast a way to get some log messages on space regarding who is slow consumer? And at the same time I don't want to enable to slow consumer.

Any comments or suggestions would be great.

-Venkat

This thread was imported from the previous forum.
For your reference, the original is available here

asked 2009-03-27 08:22:16 -0500

venkatg gravatar image

updated 2013-08-08 09:52:00 -0500

jaissefsfex gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

What is the basis for the slow consumption scenario? Are you referring to embedded workers who are not fast enough, or is it remote notification clients?

answered 2009-03-27 09:52:03 -0500

nirpaz gravatar image
edit flag offensive delete link more

Comments

Thanks for the reply. I am looking at remote notification client.

Basically atleast I should be telling one of the clients connected to space is slow consumer. As I am using spaceProxy for writing/updating to space, connection tab in space browser is showing all clients connected to the cluster.

One more Question: Is there a way to get the clients IP/hostname (some client information) when they are registering for notifications through space filter?

-Venkat

venkatg gravatar imagevenkatg ( 2009-03-27 11:16:01 -0500 )edit

If you have slow consumers enabled and have the com.gigaspaces.lrmi logger in FINE Level you will see the following messages when a slow consumer has been identified:

    "Sleeping - waiting for slow consumer: " + address +
            "\nRetry = " + (_slowConsumerRetries - retriesLeft) +
            "\nSlowConsumerThroughput = " + _slowConsumerThroughput +
            "\nSlowConsumerRetries = " + _slowConsumerRetries +
            "\nSlowConsumerLatency = " + _slowConsumerLatency;


    "Closing slow consumer: " + address +
            "\nSlowConsumerThroughput=" + _slowConsumerThroughput +
            "\nSlowConsumerRetries=" + _slowConsumerRetries +
            "\nSlowConsumerLatency=" + _slowConsumerLatency;

You can write a "marker object" to the space before/after registering for notifications to have the full info you need for each client registered for notifications.

Shay

shay hassidim gravatar imageshay hassidim ( 2009-03-27 13:22:27 -0500 )edit

Thanks shay given very helpful information. Following is some thing I am playing with let me know if thats a good thing todo or not.

Basically I enabled log levels as you suggested and enabled slow consumer. I configured space with slow consumer values latency 60 seconds and retries to 1000. Basically client is not disconnect whole day. I am watching logs for slow consumer message and will be taking respective required action.

Question: Will there be any effects/drawbacks on spaces with this approach.

-Venkat

venkatg gravatar imagevenkatg ( 2009-04-02 12:36:58 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2009-03-27 08:22:16 -0500

Seen: 59 times

Last updated: Mar 27 '09