[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-07 Thread Eno Thereska (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947054#comment-14947054
 ] 

Eno Thereska commented on KAFKA-2587:
-

I get this too on trunk, under Ubuntu but not MacOS
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename:   trusty


> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-06 Thread Flavio Junqueira (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944700#comment-14944700
 ] 

Flavio Junqueira commented on KAFKA-2587:
-

bq. is it possible that the sequential node doesn't exist yet on the new ZK 
server?

When a client re-connects to a different server, it makes sure that the server 
has seen at least as many updates as the previous one by checking the latest 
zxid of the new server it is connecting to. Consequently, if a znode Z is 
observable to a client while the client is connected to server A and the client 
successfully re-connects to B, then the client must be able to see Z through B.

Assuming that the znodes under /acl_changes aren't ephemerals and haven't been 
deleted, it is not possible that the Authorizer receives a watch  notification 
while connected to server A, re-connects to server B, and doesn't see the 
change that triggered the notification while connected to B. 

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-05 Thread Jun Rao (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943705#comment-14943705
 ] 

Jun Rao commented on KAFKA-2587:


[~parth.brahmbhatt], the issue for the above test failure can be due to the 
following. Even though we update the acl cache directly when we add or remove 
acls, the acl cache will be updated again by the ZK listener thread. So, what 
can happen is that: (1) we make an acl change and update the acl cache and a ZK 
event is fired and it reads the acl change and is about to apply the update to 
the acl cache, (2) we make a second acl change and update the acl cache 
directly, (3) the logic in the ZK event in (1) continues and will temporarily 
update the acl cache with just the first acl change. So if you test the acl at 
this moment and expect both acl changes to be in the cache, the assertion will 
fail. That seems to be what's happening in SimpleAclAuthorizerTest.scala:214 
since we made multiple acl changes before the assertion. If we wrap the 
assertion in line 214 in waitUntil(), the assertion should eventually succeed.

Also, currently, addAcl() and removeAcl() In SimpleAclAuthorizer directly 
update the acl cache as well as triggering a ZK event. I am wondering if it's 
simpler to not update the acl cache directly and only let the ZK event to do 
the update. There is no guarantee that we will see the latest acl even if we 
update the cache directly (see the above case). Then, we just need to wrap all 
acl assertions in SimpleAclAuthorizerTest with waitUntil.

Finally, it seems that the issue with "Simultaneously Consistent Cross-Client 
Views" only happens when you have multiple ZK servers in the ensemble. In unit 
tests, we only have a single ZK server.

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-05 Thread Parth Brahmbhatt (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943792#comment-14943792
 ] 

Parth Brahmbhatt commented on KAFKA-2587:
-

https://github.com/apache/kafka/pull/277/files

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-05 Thread Jun Rao (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944171#comment-14944171
 ] 

Jun Rao commented on KAFKA-2587:


As for seeing consistent view in ZK, I am not 100% sure about some of the 
corner cases. Let me describe the scenarios and see if [~fpj] can help answer. 
The way that we propagate the acl changes is the following.

1. Acl cli writes the new acl A for a resource R under /acls/R -> A and also 
writes a sequential node under /acl_changes with R as the value to indicate 
that the acl from resource R has changed.
2. The Authorizer subscribes to child changes to /acl_changes. When the watcher 
is fired, it reads all new sequential nodes under /acl_changes. From those 
sequential nodes, it knows what resources' acls have changed and it will read 
the latest acl for R from /acls/R.

A a couple of questions on this in some of the corner cases. If Authorizer 
loses the ZK connection (session is still valid) btw the time that it reads all 
child nodes under /acl_changes and that it reads the value of the sequential 
node, when the Authorizer reconnects to another ZK server and tries to re-read 
the sequential node, is it possible that the sequential node doesn't exist yet 
on the new ZK server? If so, will the child watcher be fired again when the 
sequential node is propagated to the new ZK server? 

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-05 Thread Ismael Juma (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943378#comment-14943378
 ] 

Ismael Juma commented on KAFKA-2587:


Another failure, output looks different:

kafka.security.auth.SimpleAclAuthorizerTest > testAclManagementAPIs FAILED
java.lang.AssertionError: expected: Set(User:bob has Allow 
permission for operations: Read from hosts: *), Cluster:* -> Set(User:bob has 
Allow permission for operations: Read from hosts: host1), 
Topic:86ea4eba-dba9-4500-8d8a-546f70763860 -> Set(User:alice has Allow 
permission for operations: Write from hosts: host1, User:bob has Allow 
permission for operations: Write from hosts: host2, User:bob has Allow 
permission for operations: Read from hosts: host2, User:alice has Allow 
permission for operations: Read from hosts: host1, User:bob has Allow 
permission for operations: Read from hosts: *), 
ConsumerGroup:test-ConsumerGroup -> Set(User:alice has Allow permission for 
operations: Write from hosts: host1, User:bob has Allow permission for 
operations: Write from hosts: host2, User:bob has Allow permission for 
operations: Read from hosts: host2, User:alice has Allow permission for 
operations: Read from hosts: host1, User:bob has Allow permission for 
operations: Read from hosts: *), ConsumerGroup:* -> Set(User:alice has Allow 
permission for operations: Write from hosts: host1, User:bob has Allow 
permission for operations: Write from hosts: host2, User:bob has Allow 
permission for operations: Read from hosts: host2, User:alice has Allow 
permission for operations: Read from hosts: host1, User:bob has Allow 
permission for operations: Read from hosts: *))> but was: 
Set(User:bob has Allow permission for operations: Read from hosts: *), 
Cluster:* -> Set(User:bob has Allow permission for operations: Read from hosts: 
host1), Topic:86ea4eba-dba9-4500-8d8a-546f70763860 -> Set(User:bob has Allow 
permission for operations: Write from hosts: host2, User:alice has Allow 
permission for operations: Write from hosts: host1, User:alice has Allow 
permission for operations: Read from hosts: host1, User:bob has Allow 
permission for operations: Read from hosts: host2), 
ConsumerGroup:test-ConsumerGroup -> Set(User:alice has Allow permission for 
operations: Write from hosts: host1, User:bob has Allow permission for 
operations: Write from hosts: host2, User:bob has Allow permission for 
operations: Read from hosts: host2, User:alice has Allow permission for 
operations: Read from hosts: host1, User:bob has Allow permission for 
operations: Read from hosts: *), ConsumerGroup:* -> Set(User:alice has Allow 
permission for operations: Write from hosts: host1, User:bob has Allow 
permission for operations: Write from hosts: host2, User:bob has Allow 
permission for operations: Read from hosts: host2, User:alice has Allow 
permission for operations: Read from hosts: host1, User:bob has Allow 
permission for operations: Read from hosts: *))>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
kafka.security.auth.SimpleAclAuthorizerTest.testAclManagementAPIs(SimpleAclAuthorizerTest.scala:214)

https://builds.apache.org/job/kafka-trunk-git-pr/670/console

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-02 Thread Parth Brahmbhatt (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14941474#comment-14941474
 ] 

Parth Brahmbhatt commented on KAFKA-2587:
-

I looked at the code to reason around why this can happen. The state reported 
is indeed one of the valid states during our test 
https://github.com/apache/kafka/blob/5764e54de147af81aac85acc00687c23e9646a5c/core/src/test/scala/unit/kafka/security/auth/SimpleAclAuthorizerTest.scala#L217

After that line we actually remove all acls for that resource, add one acl back 
to it and remove that one acl. All those steps pass verification. 
https://github.com/apache/kafka/blob/5764e54de147af81aac85acc00687c23e9646a5c/core/src/test/scala/unit/kafka/security/auth/SimpleAclAuthorizerTest.scala#L225
 and 
https://github.com/apache/kafka/blob/5764e54de147af81aac85acc00687c23e9646a5c/core/src/test/scala/unit/kafka/security/auth/SimpleAclAuthorizerTest.scala#L226

Given we are using the same instance of the authorizer the cache of that 
instance is immediately updated for both add and remove. 
https://github.com/apache/kafka/blob/5764e54de147af81aac85acc00687c23e9646a5c/core/src/main/scala/kafka/security/auth/SimpleAclAuthorizer.scala#L171
https://github.com/apache/kafka/blob/5764e54de147af81aac85acc00687c23e9646a5c/core/src/main/scala/kafka/security/auth/SimpleAclAuthorizer.scala#L189

The only other place that can update the cache is notification handler as part 
of handling acl-changed notification. 
https://github.com/apache/kafka/blob/5764e54de147af81aac85acc00687c23e9646a5c/core/src/main/scala/kafka/security/auth/SimpleAclAuthorizer.scala#L269

However in that case we read the data from zookeeper and then update the cache. 
If the notifications processing was delayed for some reason, it should still 
read the acls from zk and then update the cache. 
There are pathological cases that can lead to this failure , for example:
1) Notification handler starts, reads acls from zk and a thread switch happens 
before it can update the cache
2) All the other cache updates go through (remove resource, add the acl, remove 
the acl). 
3) Before verification finishes for the last "remove one acl" a thread switch 
happens and notification handler update the cache with stale acls that it read 
before. 

Even with this case there should be follow up notifications about adding an acl 
and removing an acl which should again cause the notification process to read 
state from zookeeper and update the cache to correct state. Plus this seems 
unlikely enough that it would not happen every other day.

I will continue to look into this. In the meantime if this is a continuous dev 
pain, we can remove the last 3 lines of test that removes the last acl and 
tries to verify that the zookeeper path is deleted. 

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-10-02 Thread Parth Brahmbhatt (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14941533#comment-14941533
 ] 

Parth Brahmbhatt commented on KAFKA-2587:
-

Hey Ismael,

As mentioned above, in production given all notifications will be processed 
sequentially and as part of each notification we read the acls from zookeeper 
(source of truth) this issue should not happen in production as long as 
zookeeper guarantees read after write consistency. We may run into this issue 
in the case where we observe inconsistency due to zookeeper not supporting 
"Simultaneously Consistent Cross-Client Views". Please see Notes section in 
http://zookeeper.apache.org/doc/trunk/zookeeperProgrammers.html#ch_zkGuarantees.
 

I looked at the zkClient code to see if we can call sync before read to avoid 
any consistency concerns but zkClient does not support sync.

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-09-29 Thread Jason Gustafson (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936102#comment-14936102
 ] 

Jason Gustafson commented on KAFKA-2587:


[~parth.brahmbhatt] Can you take a look at this test failure? 
https://builds.apache.org/job/kafka-trunk-git-pr/615/console

Here's the failure snippet:
{code}
kafka.security.auth.SimpleAclAuthorizerTest > testAclManagementAPIs FAILED
java.lang.AssertionError: changes not propagated in timeout period. 
expected Set() but got Set(User:bob has Allow permission for operations: Write 
from hosts: host2, User:alice has Allow permission for operations: Write from 
hosts: host1, User:bob has Allow permission for operations: Read from hosts: 
host2)
at org.junit.Assert.fail(Assert.java:88)
at kafka.utils.TestUtils$.waitUntilTrue(TestUtils.scala:654)
at 
kafka.security.auth.SimpleAclAuthorizerTest.changeAclAndVerify(SimpleAclAuthorizerTest.scala:229)
at 
kafka.security.auth.SimpleAclAuthorizerTest.testAclManagementAPIs(SimpleAclAuthorizerTest.scala:191)
{code}

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
> Fix For: 0.9.0.0
>
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-09-28 Thread Ismael Juma (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14934222#comment-14934222
 ] 

Ismael Juma commented on KAFKA-2587:


Another failure:

https://builds.apache.org/job/Kafka-trunk/647/console

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-09-28 Thread Parth Brahmbhatt (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14934498#comment-14934498
 ] 

Parth Brahmbhatt commented on KAFKA-2587:
-

[~ijuma] I tried to reproduce this locally by running the test in loop for 50 
times and it never failed. 

{code}
for i in `seq 1 50`; do ./gradlew clean core:test 
-Dtest.single=SimpleAclAuthorizerTest; done
{code}

Just analyzing the failure shows that the transient failure is reported during 
removal of the acl on this line. 
https://github.com/apache/kafka/blob/0990b6ba6a28276f79a1a8bfaf48455c6eddfa1f/core/src/test/scala/unit/kafka/security/auth/SimpleAclAuthorizerTest.scala#L190

Looking at the code given we update the local authorizer's cache immediately I 
am not entirely sure why would we see transient failures. I have modified the 
failure message to indicate a little bit more debug info and I have bumped up 
the timeout from 5 seconds to 10 seconds in case notification processing delay 
interleaved with the changes made to cache is somehow resulting in this failure.
 
{code}
kafka.security.auth.SimpleAclAuthorizerTest > testAclManagementAPIs FAILED
java.lang.AssertionError: changes not propagated in timeout period.
at org.junit.Assert.fail(Assert.java:88)
at kafka.utils.TestUtils$.waitUntilTrue(TestUtils.scala:655)
at 
kafka.security.auth.SimpleAclAuthorizerTest.changeAclAndVerify(SimpleAclAuthorizerTest.scala:229)
at 
kafka.security.auth.SimpleAclAuthorizerTest.testAclManagementAPIs(SimpleAclAuthorizerTest.scala:190)
{code}

> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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

[jira] [Commented] (KAFKA-2587) Transient test failure: `SimpleAclAuthorizerTest`

2015-09-28 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/KAFKA-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14934499#comment-14934499
 ] 

ASF GitHub Bot commented on KAFKA-2587:
---

GitHub user Parth-Brahmbhatt opened a pull request:

https://github.com/apache/kafka/pull/260

KAFKA-2587:Increasing timeout for the test verification.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Parth-Brahmbhatt/kafka KAFKA-2587

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/260.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #260


commit bd2622297db321418e592db2edf642083d571bbb
Author: Parth Brahmbhatt 
Date:   2015-09-29T02:09:03Z

KAFKA-2587:Increasing timeout for the test verification.




> Transient test failure: `SimpleAclAuthorizerTest`
> -
>
> Key: KAFKA-2587
> URL: https://issues.apache.org/jira/browse/KAFKA-2587
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Ismael Juma
>Assignee: Parth Brahmbhatt
>
> I've seen `SimpleAclAuthorizerTest ` fail a couple of times since its recent 
> introduction. Here's one such build:
> https://builds.apache.org/job/kafka-trunk-git-pr/576/console
> [~parth.brahmbhatt], can you please take a look and see if it's an easy fix?



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