You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2015/08/03 19:59:04 UTC

[jira] [Commented] (IGNITE-1179) Futures stop working, unknown cause.

    [ https://issues.apache.org/jira/browse/IGNITE-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652189#comment-14652189 ] 

Andrey Gura commented on IGNITE-1179:
-------------------------------------

I watched logs and dumps and observed only one suspicious issue: 16 (probably all) threads from system pool waiting for IgniteCacheProxy.remove operation that invoked from future listeners. 

All jobs on worker node are completed but 50 futures on server node isn't completed. But from server.log I see that futures get completed periodically and don't hang.

So I don't understand why do you think that futures stop working. Could you please get thread dumps again in moment when futures actually hang?

> Futures stop working, unknown cause.
> ------------------------------------
>
>                 Key: IGNITE-1179
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1179
>             Project: Ignite
>          Issue Type: Bug
>          Components: compute
>            Reporter: Darren Edmonds
>            Assignee: Andrey Gura
>         Attachments: ApplicationLogsAndConfig_1.3.2.7z
>
>
> Running against Apache Ignite version: 
> ignite-core (1.3.2), ignite-spring (1.3.2), ignite-indexing (1.3.2) and ignite-slf4j (1.3.2).
> Originally built application against a Grid Gain version before moving to Apache Ignite.
> Web Application feeds jobs to the worker node(s) via it's own internal queue (client only Ignite).  After a few thousand jobs have successfully been processed, the worker and server just stop with jobs still waiting in the web server queue.  It appears that the worker node is running OK, and logs will show every job is successfully completing the render but the future on the server is not being triggered - loss of connection to node?
> I have attached the requested information to the ticket.  It's highly likely I've done something wrong rather than this being a bug with Ignite - any advice would be appreciated,
> Attachment contains:
> - Server stack
> - Worker node stack
> - Server log file (simple debug output, no output observed from Ignite set at INFO level nor any exceptions)
> - Worker log file (same setup as server log file)
> - Ignite configuration files for both server and worker.
> - Launch parameters for the java command line and tomcat7 server.
> Original forum post:
> http://apache-ignite-users.70518.x6.nabble.com/Futures-not-being-triggered-td773.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)