ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tracel <tracelister....@gmail.com>
Subject How to troubleshoot a slow client node get()
Date Wed, 13 Jul 2016 07:21:54 GMT
I have an Ignite (1.5.0.final) cache client node started in a Tomcat 8.0.32,
the client node connects to a server node started on the same machine.

Sometimes the get() need some 5 seconds, while most of the other get() need
almost no time.
I wonder how the 5 seconds was spent, how I can troubleshoot it?

I am trying but still cannot reproduce the symptom with another application,
I will keep trying but hopefully I can get someone to shed some light here.

Here is the log output, only the get() at 11:40:13 and 11:56:10 were taking
longer time:

    11:40:13,333 [ INFO] CacheService:150 - ### Before get()
    11:40:18,503 [ INFO] CacheService:152 - ### After  get()
    11:40:18,505 [ INFO] CacheService:150 - ### Before get()
    11:40:18,528 [ INFO] CacheService:152 - ### After  get()
    11:40:18,529 [ INFO] CacheService:150 - ### Before get()
    11:40:18,538 [ INFO] CacheService:152 - ### After  get()
    11:40:18,538 [ INFO] CacheService:150 - ### Before get()
    11:40:18,558 [ INFO] CacheService:152 - ### After  get()
    11:40:18,558 [ INFO] CacheService:150 - ### Before get()
    11:40:18,567 [ INFO] CacheService:152 - ### After  get()
    11:40:18,567 [ INFO] CacheService:150 - ### Before get()
    11:40:18,575 [ INFO] CacheService:152 - ### After  get()
    11:40:18,576 [ INFO] CacheService:150 - ### Before get()
    11:40:18,595 [ INFO] CacheService:152 - ### After  get()
    11:40:18,595 [ INFO] CacheService:150 - ### Before get()
    11:40:18,603 [ INFO] CacheService:152 - ### After  get()
    11:40:18,786 [ INFO] CacheService:150 - ### Before get()
    11:40:18,795 [ INFO] CacheService:152 - ### After  get()
    11:56:10,142 [ INFO] CacheService:150 - ### Before get()
    11:56:15,208 [ INFO] CacheService:152 - ### After  get()
    11:56:15,208 [ INFO] CacheService:150 - ### Before get()
    11:56:15,214 [ INFO] CacheService:152 - ### After  get()
    11:56:15,214 [ INFO] CacheService:150 - ### Before get()
    11:56:15,228 [ INFO] CacheService:152 - ### After  get()
    11:56:15,229 [ INFO] CacheService:150 - ### Before get()
    11:56:15,243 [ INFO] CacheService:152 - ### After  get()
    11:56:15,244 [ INFO] CacheService:150 - ### Before get()
    11:56:15,247 [ INFO] CacheService:152 - ### After  get()
    11:56:15,247 [ INFO] CacheService:150 - ### Before get()
    11:56:15,250 [ INFO] CacheService:152 - ### After  get()
    11:56:15,250 [ INFO] CacheService:150 - ### Before get()
    11:56:15,255 [ INFO] CacheService:152 - ### After  get()
    11:56:15,256 [ INFO] CacheService:150 - ### Before get()
    11:56:15,258 [ INFO] CacheService:152 - ### After  get()
    11:56:15,280 [ INFO] CacheService:150 - ### Before get()


The original code is quite complicated so I put a simplified version here:

        private IgniteCache<String, Vendor> cache;

	public Vendor getVendor(String vendorCode) {
                log.info("### Before get()");
		Vendor vendor = cache.get(vendorCode);
                log.info("### After  get()");
		
		if (vendor == null) {
			vendor = findVendorFromDB(vendorCode);
		}	
		
		return vendor;
	}


Thanks in advance!



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-troubleshoot-a-slow-client-node-get-tp6250.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message