[jira] [Commented] (BOOKKEEPER-998) Increased the max entry size to 5MB

2017-02-08 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on BOOKKEEPER-998:
---

Github user jvrao commented on the issue:

https://github.com/apache/bookkeeper/pull/104
  
1MB is good enough for us at least for now. Did not test anything larger.


> Increased the max entry size to 5MB
> ---
>
> Key: BOOKKEEPER-998
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-998
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> In practice we have found the Bookkeeper can handle 5MB entries without 
> issue.  We should make the {{PerChannelBookieClient.MAX_FRAME_LENGTH}}, the 
> {{BookieNettyServer.maxMessageSize}} and the 
> {{EntryLogger.MAX_SANE_ENTRY_SIZE}} size all consistent with one another, and 
> ideally 5MB.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [discuss] moving the community meeting to Friday

2017-02-08 Thread Venkateswara Rao Jujjuri 
May be it is too late; I am ok moving it Friday 8 AM

@Sijie what would you think? We also need Agenda

On Wed, Feb 8, 2017 at 9:13 AM, Enrico Olivelli  wrote:

> Sorry for bothering everybody, this week we are going to meet on Thursday?
>
> This is the link to the discussion page
> https://cwiki.apache.org/confluence/display/BOOKKEEPER/Community+Meetings
>
> Cheers
> Enrico
>
> Il mar 7 feb 2017, 15:46 Bobby Evans  ha
> scritto:
>
> > Yes I would love to join too.  We missed the last meeting invite.  In
> > general we can make time most days, especially if it is in the morning.
> >
> >
> > - Bobby
> >
> > On Tuesday, February 7, 2017, 5:21:49 AM CST, Enrico Olivelli <
> > eolive...@gmail.com> wrote:Any news ?
> > This week the meeting will be on Friday ?
> >
> > @Bobby
> > It would be great if some of your new team at Yahoo could join the
> meeting
> >
> > 2017-01-31 7:44 GMT+01:00 Enrico Olivelli :
> >
> > > For me Friday is ok too. And 8am pt is ideal for me.
> > >
> > > I hope that more guus can attend these useful meetings
> > >
> > > Enrico
> > >
> > > Il mar 31 gen 2017, 02:17 Sijie Guo  ha scritto:
> > >
> > >> It was raised in the other email thread. I'd like to pull that out to
> > >> discuss here. Is anyone good on moving the community meeting to Friday
> > >> same
> > >> time (8am pst)?
> > >>
> > >> please give us your options and we can try to coordinate here.
> > >>
> > >> - Sijie
> > >>
> > > --
> > >
> > >
> > > -- Enrico Olivelli
> > >
> >
> --
>
>
> -- Enrico Olivelli
>



-- 
Jvrao
---
First they ignore you, then they laugh at you, then they fight you, then
you win. - Mahatma Gandhi

[jira] [Assigned] (BOOKKEEPER-1000) BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing

2017-02-08 Thread Robert Joseph Evans (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BOOKKEEPER-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Joseph Evans reassigned BOOKKEEPER-1000:
---

Assignee: Kyle Nusbaum  (was: Robert Joseph Evans)

> BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing
> --
>
> Key: BOOKKEEPER-1000
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1000
> Project: Bookkeeper
>  Issue Type: Bug
>Reporter: Robert Joseph Evans
>Assignee: Kyle Nusbaum
>
> Tests in error:
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] » BKNoSuchLedgerExists
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] » BKNoSuchLedgerExists
> This has been happening in master recently both in Jenkins and on my Mac.  
> I'll try to take a look at it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (BOOKKEEPER-1000) BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing

2017-02-08 Thread Matteo Merli (JIRA) 

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

Matteo Merli commented on BOOKKEEPER-1000:
--

[~revans2] Sure, added Kyle

> BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing
> --
>
> Key: BOOKKEEPER-1000
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1000
> Project: Bookkeeper
>  Issue Type: Bug
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> Tests in error:
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] » BKNoSuchLedgerExists
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] » BKNoSuchLedgerExists
> This has been happening in master recently both in Jenkins and on my Mac.  
> I'll try to take a look at it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (BOOKKEEPER-1000) BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing

2017-02-08 Thread Robert Joseph Evans (JIRA) 

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

Robert Joseph Evans commented on BOOKKEEPER-1000:
-

[~mmerli],

Would you mind adding in [~knusbaum] as a contributor so he can take over this 
JIRA?

> BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing
> --
>
> Key: BOOKKEEPER-1000
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1000
> Project: Bookkeeper
>  Issue Type: Bug
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> Tests in error:
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] » BKNoSuchLedgerExists
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] » BKNoSuchLedgerExists
> This has been happening in master recently both in Jenkins and on my Mac.  
> I'll try to take a look at it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (BOOKKEEPER-1000) BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing

2017-02-08 Thread Robert Joseph Evans (JIRA) 

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

Robert Joseph Evans commented on BOOKKEEPER-1000:
-

It looks like this is a bug in BOOKKEEPER-873 and BOOKKEEPER-553.  Not sure how 
this test ever passed for them.  Essentially because the layout of the files 
changed for 2-4-4- to 3-4-4-4-4 it is not able to see the older ledgers.  It 
just ignores them.  It seems like we should be able to make it so that for IDs 
< max int we go with 2-4-4 and for > max int we go with 3-4-4-4-4.  Or we just 
disable this particular test because it will never work.  I would prefer to do 
the former because it provides a path towards a rolling upgrade.

[~knusbaum] said he was already looking at this so I think I will just hand it 
off to him.

> BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing
> --
>
> Key: BOOKKEEPER-1000
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1000
> Project: Bookkeeper
>  Issue Type: Bug
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> Tests in error:
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] » BKNoSuchLedgerExists
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] » BKNoSuchLedgerExists
> This has been happening in master recently both in Jenkins and on my Mac.  
> I'll try to take a look at it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (BOOKKEEPER-1000) BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing

2017-02-08 Thread Robert Joseph Evans (JIRA) 

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

Robert Joseph Evans commented on BOOKKEEPER-1000:
-

The test fails consistently for 
org.apache.bookkeeper.meta.LongHierarchicalLedgerManagerFactory.

> BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing
> --
>
> Key: BOOKKEEPER-1000
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1000
> Project: Bookkeeper
>  Issue Type: Bug
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> Tests in error:
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] » BKNoSuchLedgerExists
>   BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] » BKNoSuchLedgerExists
> This has been happening in master recently both in Jenkins and on my Mac.  
> I'll try to take a look at it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (BOOKKEEPER-999) BookKeeper client can leak threads

2017-02-08 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on BOOKKEEPER-999:
---

Github user zzsongsg commented on the issue:

https://github.com/apache/bookkeeper/pull/105
  
+1 looks good to me.


> BookKeeper client can leak threads
> --
>
> Key: BOOKKEEPER-999
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-999
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-client
>Affects Versions: 4.4.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> The client constructor
> {{BookKeeper(ClientConfiguration conf, ZooKeeper zk)}}
> in 4.4 and above will create a new NioClientSocketChannelFactory but does not 
> set the ownership of that factory to true so threads are leaked.
> This showed up as a failure in BookieRecoveryTest on MacOS where it has a 
> hard coded limit of about 2000 threads in a single process, and this test was 
> going beyond that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [discuss] moving the community meeting to Friday

2017-02-08 Thread Enrico Olivelli 
Sorry for bothering everybody, this week we are going to meet on Thursday?

This is the link to the discussion page
https://cwiki.apache.org/confluence/display/BOOKKEEPER/Community+Meetings

Cheers
Enrico

Il mar 7 feb 2017, 15:46 Bobby Evans  ha
scritto:

> Yes I would love to join too.  We missed the last meeting invite.  In
> general we can make time most days, especially if it is in the morning.
>
>
> - Bobby
>
> On Tuesday, February 7, 2017, 5:21:49 AM CST, Enrico Olivelli <
> eolive...@gmail.com> wrote:Any news ?
> This week the meeting will be on Friday ?
>
> @Bobby
> It would be great if some of your new team at Yahoo could join the meeting
>
> 2017-01-31 7:44 GMT+01:00 Enrico Olivelli :
>
> > For me Friday is ok too. And 8am pt is ideal for me.
> >
> > I hope that more guus can attend these useful meetings
> >
> > Enrico
> >
> > Il mar 31 gen 2017, 02:17 Sijie Guo  ha scritto:
> >
> >> It was raised in the other email thread. I'd like to pull that out to
> >> discuss here. Is anyone good on moving the community meeting to Friday
> >> same
> >> time (8am pst)?
> >>
> >> please give us your options and we can try to coordinate here.
> >>
> >> - Sijie
> >>
> > --
> >
> >
> > -- Enrico Olivelli
> >
>
-- 


-- Enrico Olivelli

[jira] [Created] (BOOKKEEPER-1000) BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing

2017-02-08 Thread Robert Joseph Evans (JIRA) 
Robert Joseph Evans created BOOKKEEPER-1000:
---

 Summary: BookieRecoveryTest.ensurePasswordUsedForOldLedgers failing
 Key: BOOKKEEPER-1000
 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1000
 Project: Bookkeeper
  Issue Type: Bug
Reporter: Robert Joseph Evans
Assignee: Robert Joseph Evans


Tests in error:
  BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4] » BKNoSuchLedgerExists
  BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5] » BKNoSuchLedgerExists

This has been happening in master recently both in Jenkins and on my Mac.  I'll 
try to take a look at it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (BOOKKEEPER-999) BookKeeper client can leak threads

2017-02-08 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on BOOKKEEPER-999:
---

Github user eolivelli commented on the issue:

https://github.com/apache/bookkeeper/pull/105
  
+1 this fix is good for me

maybe we should consider deprecating that constructor (add a @Deprecated 
annocation), in favour of the official Builder for BookKeeper client

@sijie  @jvrao  what do you think ?


> BookKeeper client can leak threads
> --
>
> Key: BOOKKEEPER-999
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-999
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-client
>Affects Versions: 4.4.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> The client constructor
> {{BookKeeper(ClientConfiguration conf, ZooKeeper zk)}}
> in 4.4 and above will create a new NioClientSocketChannelFactory but does not 
> set the ownership of that factory to true so threads are leaked.
> This showed up as a failure in BookieRecoveryTest on MacOS where it has a 
> hard coded limit of about 2000 threads in a single process, and this test was 
> going beyond that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (BOOKKEEPER-999) BookKeeper client can leak threads

2017-02-08 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on BOOKKEEPER-999:
---

Github user jvrao commented on the issue:

https://github.com/apache/bookkeeper/pull/105
  
+1 LGTM


> BookKeeper client can leak threads
> --
>
> Key: BOOKKEEPER-999
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-999
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-client
>Affects Versions: 4.4.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> The client constructor
> {{BookKeeper(ClientConfiguration conf, ZooKeeper zk)}}
> in 4.4 and above will create a new NioClientSocketChannelFactory but does not 
> set the ownership of that factory to true so threads are leaked.
> This showed up as a failure in BookieRecoveryTest on MacOS where it has a 
> hard coded limit of about 2000 threads in a single process, and this test was 
> going beyond that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: bookkeeper-master-git-pullrequest #210

2017-02-08 Thread Apache Jenkins Server 
See 


Changes:

[evans] BOOKKEEPER-999: Stop leaking threads in BookKeeper client

--
[...truncated 403 lines...]

---
 T E S T S
---
Running org.apache.bookkeeper.util.TestDiskChecker
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.186 sec - in 
org.apache.bookkeeper.util.TestDiskChecker
Running org.apache.bookkeeper.util.collections.ConcurrentLongLongPairHashMapTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.741 sec - in 
org.apache.bookkeeper.util.collections.ConcurrentLongLongPairHashMapTest
Running org.apache.bookkeeper.util.collections.ConcurrentOpenHashMapTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.603 sec - in 
org.apache.bookkeeper.util.collections.ConcurrentOpenHashMapTest
Running org.apache.bookkeeper.util.collections.ConcurrentLongHashMapTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.217 sec - in 
org.apache.bookkeeper.util.collections.ConcurrentLongHashMapTest
Running org.apache.bookkeeper.util.collections.ConcurrentOpenHashSetTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.349 sec - in 
org.apache.bookkeeper.util.collections.ConcurrentOpenHashSetTest
Running org.apache.bookkeeper.util.collections.ConcurrentLongHashSetTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.881 sec - in 
org.apache.bookkeeper.util.collections.ConcurrentLongHashSetTest
Running org.apache.bookkeeper.util.collections.ConcurrentLongLongHashMapTest
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.079 sec - in 
org.apache.bookkeeper.util.collections.ConcurrentLongLongHashMapTest
Running org.apache.bookkeeper.conf.NoSystemPropertiesConfigurationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.168 sec - in 
org.apache.bookkeeper.conf.NoSystemPropertiesConfigurationTest
Running org.apache.bookkeeper.conf.SystemPropertiesConfigurationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.193 sec - in 
org.apache.bookkeeper.conf.SystemPropertiesConfigurationTest
Running org.apache.bookkeeper.auth.TestAuth
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.828 sec - 
in org.apache.bookkeeper.auth.TestAuth
Running org.apache.bookkeeper.bookie.CreateNewLogTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.6 sec - in 
org.apache.bookkeeper.bookie.CreateNewLogTest
Running org.apache.bookkeeper.bookie.IndexCorruptionTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.287 sec - in 
org.apache.bookkeeper.bookie.IndexCorruptionTest
Running org.apache.bookkeeper.bookie.BookieShutdownTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.38 sec - in 
org.apache.bookkeeper.bookie.BookieShutdownTest
Running org.apache.bookkeeper.bookie.EntryLogTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.394 sec - in 
org.apache.bookkeeper.bookie.EntryLogTest
Running org.apache.bookkeeper.bookie.CompactionTest
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 96.541 sec - 
in org.apache.bookkeeper.bookie.CompactionTest
Running org.apache.bookkeeper.bookie.IndexPersistenceMgrTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.298 sec - in 
org.apache.bookkeeper.bookie.IndexPersistenceMgrTest
Running org.apache.bookkeeper.bookie.TestLedgerDirsManager
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.463 sec - in 
org.apache.bookkeeper.bookie.TestLedgerDirsManager
Running org.apache.bookkeeper.bookie.BookieJournalTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.646 sec - in 
org.apache.bookkeeper.bookie.BookieJournalTest
Running org.apache.bookkeeper.bookie.UpgradeTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.489 sec - in 
org.apache.bookkeeper.bookie.UpgradeTest
Running org.apache.bookkeeper.bookie.UpdateCookieCmdTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.954 sec - in 
org.apache.bookkeeper.bookie.UpdateCookieCmdTest
Running org.apache.bookkeeper.bookie.CookieTest
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.127 sec - in 
org.apache.bookkeeper.bookie.CookieTest
Running org.apache.bookkeeper.bookie.LedgerCacheTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.247 sec - in 
org.apache.bookkeeper.bookie.LedgerCacheTest
Running org.apache.bookkeeper.bookie.TestSyncThread
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.917 sec - in 
org.apache.bookkeeper.bookie.TestSyncThread
Running org.apache.bookkeeper.bookie.BookieInitializationTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.667 sec - in 
org.apache.bookkeeper.bookie.BookieInitializationTest
Runn

[jira] [Commented] (BOOKKEEPER-999) BookKeeper client can leak threads

2017-02-08 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on BOOKKEEPER-999:
---

GitHub user revans2 opened a pull request:

https://github.com/apache/bookkeeper/pull/105

BOOKKEEPER-999: Stop leaking threads in BookKeeper client



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

$ git pull https://github.com/revans2/bookkeeper BOOKKEEPER-999

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

https://github.com/apache/bookkeeper/pull/105.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 #105


commit b0e9a3679f76771e80cefbe67de7a1ed33fc42ad
Author: Robert (Bobby) Evans 
Date:   2017-02-08T14:45:30Z

BOOKKEEPER-999: Stop leaking threads in BookKeeper client




> BookKeeper client can leak threads
> --
>
> Key: BOOKKEEPER-999
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-999
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-client
>Affects Versions: 4.4.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> The client constructor
> {{BookKeeper(ClientConfiguration conf, ZooKeeper zk)}}
> in 4.4 and above will create a new NioClientSocketChannelFactory but does not 
> set the ownership of that factory to true so threads are leaked.
> This showed up as a failure in BookieRecoveryTest on MacOS where it has a 
> hard coded limit of about 2000 threads in a single process, and this test was 
> going beyond that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (BOOKKEEPER-999) BookKeeper client can leak threads

2017-02-08 Thread Robert Joseph Evans (JIRA) 
Robert Joseph Evans created BOOKKEEPER-999:
--

 Summary: BookKeeper client can leak threads
 Key: BOOKKEEPER-999
 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-999
 Project: Bookkeeper
  Issue Type: Bug
  Components: bookkeeper-client
Affects Versions: 4.4.0
Reporter: Robert Joseph Evans
Assignee: Robert Joseph Evans


The client constructor

{{BookKeeper(ClientConfiguration conf, ZooKeeper zk)}}

in 4.4 and above will create a new NioClientSocketChannelFactory but does not 
set the ownership of that factory to true so threads are leaked.

This showed up as a failure in BookieRecoveryTest on MacOS where it has a hard 
coded limit of about 2000 threads in a single process, and this test was going 
beyond that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

FINAL REMINDER: CFP for ApacheCon closes February 11th

2017-02-08 Thread Rich Bowen 
Dear Apache Enthusiast,

This is your FINAL reminder that the Call for Papers (CFP) for ApacheCon
Miami is closing this weekend - February 11th. This is your final
opportunity to submit a talk for consideration at this event.

This year, we are running several mini conferences in conjunction with
the main event, so if you're submitting for one of those events, please
pay attention to the instructions below.

Apache: Big Data
* Event information:
http://events.linuxfoundation.org/events/apache-big-data-north-america
* CFP:
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp

Apache: IoT (Internet of Things)
* Event Information: http://us.apacheiot.org/
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'IoT' in the Target Audience field)

CloudStack Collaboration Conference
* Event information: http://us.cloudstackcollab.org/
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'CloudStack' in the Target Audience field)

FlexJS Summit
* Event information - http://us.apacheflexjs.org/
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'Flex' in the Target Audience field)

TomcatCon
* Event information - https://tomcat.apache.org/conference.html
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
(Indicate 'Tomcat' in the Target Audience field)

All other topics and projects
* Event information -
http://events.linuxfoundation.org/events/apachecon-north-america/program/about
* CFP -
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp

Admission to any of these events also grants you access to all of the
others.

Thanks, and we look forward to seeing you in Miami!

-- 
Rich Bowen
VP Conferences, Apache Software Foundation
rbo...@apache.org
Twitter: @apachecon



(You are receiving this email because you are subscribed to a dev@ or
users@ list of some Apache Software Foundation project. If you do not
wish to receive email from these lists any more, you must follow that
list's unsubscription procedure. View the headers of this message for
unsubscription instructions.)

Build failed in Jenkins: bookkeeper-master #1652

2017-02-08 Thread Apache Jenkins Server 
See 

--
[...truncated 375 lines...]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 114 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ bookkeeper-server 
---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.

---
 T E S T S
---
Running org.apache.bookkeeper.metastore.TestMetaStore
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.315 sec - in 
org.apache.bookkeeper.metastore.TestMetaStore
Running org.apache.bookkeeper.proto.TestDeathwatcher
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.129 sec - in 
org.apache.bookkeeper.proto.TestDeathwatcher
Running org.apache.bookkeeper.proto.TestBackwardCompatCMS42
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.327 sec - in 
org.apache.bookkeeper.proto.TestBackwardCompatCMS42
Running org.apache.bookkeeper.proto.TestPerChannelBookieClient
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.862 sec - in 
org.apache.bookkeeper.proto.TestPerChannelBookieClient
Running org.apache.bookkeeper.proto.NetworkLessBookieTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.866 sec - in 
org.apache.bookkeeper.proto.NetworkLessBookieTest
Running org.apache.bookkeeper.proto.TestBKStats
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.148 sec - in 
org.apache.bookkeeper.proto.TestBKStats
Running org.apache.bookkeeper.client.RoundRobinDistributionScheduleTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.177 sec - in 
org.apache.bookkeeper.client.RoundRobinDistributionScheduleTest
Running org.apache.bookkeeper.client.TestWatchEnsembleChange
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.08 sec - in 
org.apache.bookkeeper.client.TestWatchEnsembleChange
Running org.apache.bookkeeper.client.GenericEnsemblePlacementPolicyTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.46 sec - in 
org.apache.bookkeeper.client.GenericEnsemblePlacementPolicyTest
Running org.apache.bookkeeper.client.TestAddEntryQuorumTimeout
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.992 sec - in 
org.apache.bookkeeper.client.TestAddEntryQuorumTimeout
Running org.apache.bookkeeper.client.TestRackawareEnsemblePlacementPolicy
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.86 sec - in 
org.apache.bookkeeper.client.TestRackawareEnsemblePlacementPolicy
Running org.apache.bookkeeper.client.BookKeeperTest
Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.808 sec - 
in org.apache.bookkeeper.client.BookKeeperTest
Running 
org.apache.bookkeeper.client.TestRackawareEnsemblePlacementPolicyUsingScript
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.52 sec - in 
org.apache.bookkeeper.client.TestRackawareEnsemblePlacementPolicyUsingScript
Running org.apache.bookkeeper.client.TestReadTimeout
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.654 sec - in 
org.apache.bookkeeper.client.TestReadTimeout
Running org.apache.bookkeeper.client.SlowBookieTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.933 sec - in 
org.apache.bookkeeper.client.SlowBookieTest
Running org.apache.bookkeeper.client.TestTryReadLastConfirmed
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.852 sec - in 
org.apache.bookkeeper.client.TestTryReadLastConfirmed
Running org.apache.bookkeeper.client.LocalBookKeeperTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.972 sec - in 
org.apache.bookkeeper.client.LocalBookKeeperTest
Running org.apache.bookkeeper.client.UpdateLedgerCmdTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.442 sec - in 
org.apache.bookkeeper.client.UpdateLedgerCmdTest
Running org.apache.bookkeeper.client.BookieWriteLedgersWithDifferentDigestsTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.84 sec - in 
org.apache.bookkeeper.client.BookieWriteLedgersWithDifferentDigestsTest
Running org.apache.bookkeeper.client.TestFencing
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.96 sec - in 
org.apache.bookkeeper.client.TestFencing
Running org.apache.bookkeeper.client.BookieWriteLedgerTest
Tests run: 96, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 54.07 sec - in 
org.apache.bookkeeper.client.BookieWriteLedgerTest
Running org.apache.bookkeeper.client.ListLedgersTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.124 sec - in 
org.apache.bookkeeper.client.ListLedgersTest
Running org.apache.bookkeeper.client.BookKeeperCloseTest
Tests run: 10, Failures: 0, Errors: 0, Skip