[jira] [Commented] (SOLR-11771) Overseer can never process some last messages

2018-01-05 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314302#comment-16314302
 ] 

ASF subversion and git services commented on SOLR-11771:


Commit 169850f90d0db65b3b9490384a8e542e478960e5 in lucene-solr's branch 
refs/heads/branch_7x from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=169850f ]

SOLR-11771: Move CHANGES entry to the right version


> Overseer can never process some last messages
> -
>
> Key: SOLR-11771
> URL: https://issues.apache.org/jira/browse/SOLR-11771
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Cao Manh Dat
>
> I met this problem when some tests get failed because timeout on creating a 
> new collection. The case here is
> 1. Overseer call DQ.peekElements with LONG.MAX_VALUE timeout.
> 2. DQ fetch children from ZK but it is empty.
> 3. At the same time with 2, a set LEADER message is enqueued, 
> {{changed.signalAll()}} already called.
> 4. The call {{changed.awaitNanos(waitNanos)}} is never end because no new 
> messages get enqueued after this point.
> The fix here is trivial, the call peekElements should have a timeout of 2 
> seconds, that will be appropriate in most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-11771) Overseer can never process some last messages

2018-01-05 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314301#comment-16314301
 ] 

ASF subversion and git services commented on SOLR-11771:


Commit 8eed452ce7a5030bdcde5d283ca2f35e4546d478 in lucene-solr's branch 
refs/heads/branch_7x from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8eed452 ]

SOLR-11771: Overseer can never process some last messages


> Overseer can never process some last messages
> -
>
> Key: SOLR-11771
> URL: https://issues.apache.org/jira/browse/SOLR-11771
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Cao Manh Dat
>
> I met this problem when some tests get failed because timeout on creating a 
> new collection. The case here is
> 1. Overseer call DQ.peekElements with LONG.MAX_VALUE timeout.
> 2. DQ fetch children from ZK but it is empty.
> 3. At the same time with 2, a set LEADER message is enqueued, 
> {{changed.signalAll()}} already called.
> 4. The call {{changed.awaitNanos(waitNanos)}} is never end because no new 
> messages get enqueued after this point.
> The fix here is trivial, the call peekElements should have a timeout of 2 
> seconds, that will be appropriate in most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-11771) Overseer can never process some last messages

2018-01-05 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314300#comment-16314300
 ] 

ASF subversion and git services commented on SOLR-11771:


Commit dd2c90d7680a54d3eefb43b26cde4c2ede265928 in lucene-solr's branch 
refs/heads/branch_7_2 from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=dd2c90d ]

SOLR-11771: Overseer can never process some last messages


> Overseer can never process some last messages
> -
>
> Key: SOLR-11771
> URL: https://issues.apache.org/jira/browse/SOLR-11771
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Cao Manh Dat
>
> I met this problem when some tests get failed because timeout on creating a 
> new collection. The case here is
> 1. Overseer call DQ.peekElements with LONG.MAX_VALUE timeout.
> 2. DQ fetch children from ZK but it is empty.
> 3. At the same time with 2, a set LEADER message is enqueued, 
> {{changed.signalAll()}} already called.
> 4. The call {{changed.awaitNanos(waitNanos)}} is never end because no new 
> messages get enqueued after this point.
> The fix here is trivial, the call peekElements should have a timeout of 2 
> seconds, that will be appropriate in most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-11771) Overseer can never process some last messages

2018-01-05 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314297#comment-16314297
 ] 

ASF subversion and git services commented on SOLR-11771:


Commit 0d5581177423aef95489351e07b2169150a9c102 in lucene-solr's branch 
refs/heads/master from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0d55811 ]

SOLR-11771: Move CHANGES entry to the right version


> Overseer can never process some last messages
> -
>
> Key: SOLR-11771
> URL: https://issues.apache.org/jira/browse/SOLR-11771
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Cao Manh Dat
>
> I met this problem when some tests get failed because timeout on creating a 
> new collection. The case here is
> 1. Overseer call DQ.peekElements with LONG.MAX_VALUE timeout.
> 2. DQ fetch children from ZK but it is empty.
> 3. At the same time with 2, a set LEADER message is enqueued, 
> {{changed.signalAll()}} already called.
> 4. The call {{changed.awaitNanos(waitNanos)}} is never end because no new 
> messages get enqueued after this point.
> The fix here is trivial, the call peekElements should have a timeout of 2 
> seconds, that will be appropriate in most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-11771) Overseer can never process some last messages

2018-01-05 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314296#comment-16314296
 ] 

ASF subversion and git services commented on SOLR-11771:


Commit b8b00786f377af30e3572282e89dbbd32fbef742 in lucene-solr's branch 
refs/heads/master from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b8b00786 ]

SOLR-11771: Overseer can never process some last messages


> Overseer can never process some last messages
> -
>
> Key: SOLR-11771
> URL: https://issues.apache.org/jira/browse/SOLR-11771
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Cao Manh Dat
>
> I met this problem when some tests get failed because timeout on creating a 
> new collection. The case here is
> 1. Overseer call DQ.peekElements with LONG.MAX_VALUE timeout.
> 2. DQ fetch children from ZK but it is empty.
> 3. At the same time with 2, a set LEADER message is enqueued, 
> {{changed.signalAll()}} already called.
> 4. The call {{changed.awaitNanos(waitNanos)}} is never end because no new 
> messages get enqueued after this point.
> The fix here is trivial, the call peekElements should have a timeout of 2 
> seconds, that will be appropriate in most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-11771) Overseer can never process some last messages

2017-12-18 Thread Cao Manh Dat (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296011#comment-16296011
 ] 

Cao Manh Dat commented on SOLR-11771:
-

[~dsmiley] Only since SOLR-11443 get committed so only 7.2 get affected.

> Overseer can never process some last messages
> -
>
> Key: SOLR-11771
> URL: https://issues.apache.org/jira/browse/SOLR-11771
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Cao Manh Dat
>
> I met this problem when some tests get failed because timeout on creating a 
> new collection. The case here is
> 1. Overseer call DQ.peekElements with LONG.MAX_VALUE timeout.
> 2. DQ fetch children from ZK but it is empty.
> 3. At the same time with 2, a set LEADER message is enqueued, 
> {{changed.signalAll()}} already called.
> 4. The call {{changed.awaitNanos(waitNanos)}} is never end because no new 
> messages get enqueued after this point.
> The fix here is trivial, the call peekElements should have a timeout of 2 
> seconds, that will be appropriate in most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-11771) Overseer can never process some last messages

2017-12-18 Thread David Smiley (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295476#comment-16295476
 ] 

David Smiley commented on SOLR-11771:
-

Does this appear to be a long-standing problem or only with a particular recent 
version?

> Overseer can never process some last messages
> -
>
> Key: SOLR-11771
> URL: https://issues.apache.org/jira/browse/SOLR-11771
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Cao Manh Dat
>
> I met this problem when some tests get failed because timeout on creating a 
> new collection. The case here is
> 1. Overseer call DQ.peekElements with LONG.MAX_VALUE timeout.
> 2. DQ fetch children from ZK but it is empty.
> 3. At the same time with 2, a set LEADER message is enqueued, 
> {{changed.signalAll()}} already called.
> 4. The call {{changed.awaitNanos(waitNanos)}} is never end because no new 
> messages get enqueued after this point.
> The fix here is trivial, the call peekElements should have a timeout of 2 
> seconds, that will be appropriate in most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org