[jira] Commented: (ZOOKEEPER-276) Bookkeeper contribution

2009-02-08 Thread Flavio Paiva Junqueira (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671584#action_12671584
 ] 

Flavio Paiva Junqueira commented on ZOOKEEPER-276:
--

Dhruba, That's an excellent question. We are still to document it in detail. 
Regarding your question, writes are reliable: when a bookie acknowledges 
receipt of an entry, it is on disk.

> Bookkeeper contribution
> ---
>
> Key: ZOOKEEPER-276
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-276
> Project: Zookeeper
>  Issue Type: New Feature
>Reporter: Luca Telloli
>Assignee: Flavio Paiva Junqueira
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, 
> ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, 
> ZOOKEEPER-276.patch, ZOOKEEPER-276.patch
>
>
> BookKeeper is a system to reliably log streams of records. In BookKeeper, 
> servers are "bookies", log streams are "ledgers", and each unit of a log (aka 
> record) is a "ledger entry". BookKeeper is designed to be reliable; bookies, 
> the servers that store ledgers can be byzantine, which means that some subset 
> of the bookies can fail, corrupt data, discard data, but as long as there are 
> enough correctly behaving servers the service as a whole behaves correctly; 
> the meta data for BookKeeper is stored in ZooKeeper.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Build failed in Hudson: ZooKeeper-trunk #223

2009-02-08 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/223/changes

--
[...truncated 61219 lines...]
[junit] 2009-02-08 11:49:01,509 - INFO  
[NIOServerCxn.Factory:33221:nioservercnxn$fact...@176] - NIOServerCnxn factory 
exited run method
[junit] 2009-02-08 11:49:01,510 - INFO  
[ProcessThread:-1:preprequestproces...@111] - PrepRequestProcessor exited loop!
[junit] 2009-02-08 11:49:01,510 - INFO  
[SyncThread:0:syncrequestproces...@117] - SyncRequestProcessor exited!
[junit] 2009-02-08 11:49:01,510 - INFO  [main:finalrequestproces...@265] - 
shutdown of request processor complete
[junit] 2009-02-08 11:49:01,609 - INFO  [main:clientb...@306] - STARTING 
server
[junit] 2009-02-08 11:49:01,610 - INFO  [main:zookeeperser...@156] - 
Created server
[junit] 2009-02-08 11:49:01,611 - INFO  [main:files...@71] - Reading 
snapshot 
http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/ws/trunk/build/test/tmp/test5752499087242004722.junit.dir/version-2/snapshot.0
 
[junit] 2009-02-08 11:49:01,612 - INFO  [main:filetxnsnap...@198] - 
Snapshotting: 3
[junit] 2009-02-08 11:49:01,614 - INFO  
[NIOServerCxn.Factory:33221:nioserverc...@621] - Processing stat command from 
/127.0.0.1:36681
[junit] 2009-02-08 11:49:01,614 - WARN  
[NIOServerCxn.Factory:33221:nioserverc...@417] - Exception causing close of 
session 0x0 due to java.io.IOException: closing
[junit] 2009-02-08 11:49:01,615 - INFO  
[NIOServerCxn.Factory:33221:nioserverc...@752] - closing session:0x0 
NIOServerCnxn: java.nio.channels.SocketChannel[connected local=/127.0.0.1:33221 
remote=/127.0.0.1:36681]
[junit] 2009-02-08 11:49:03,000 - INFO  
[SessionTracker:sessiontrackeri...@142] - SessionTrackerImpl exited loop!
[junit] 2009-02-08 11:49:03,000 - INFO  
[SessionTracker:sessiontrackeri...@142] - SessionTrackerImpl exited loop!
[junit] 2009-02-08 11:49:03,335 - INFO  
[main-SendThread:clientcnxn$sendthr...@800] - Attempting connection to server 
/127.0.0.1:33221
[junit] 2009-02-08 11:49:03,336 - INFO  
[main-SendThread:clientcnxn$sendthr...@716] - Priming connection to 
java.nio.channels.SocketChannel[connected local=/127.0.0.1:36682 
remote=/127.0.0.1:33221]
[junit] 2009-02-08 11:49:03,336 - INFO  
[main-SendThread:clientcnxn$sendthr...@868] - Server connection successful
[junit] 2009-02-08 11:49:03,336 - INFO  
[NIOServerCxn.Factory:33221:nioserverc...@503] - Connected to /127.0.0.1:36682 
lastZxid 3
[junit] 2009-02-08 11:49:03,337 - INFO  
[NIOServerCxn.Factory:33221:nioserverc...@881] - Finished init of 
0x11f55b815b3 valid:true
[junit] 2009-02-08 11:49:03,337 - INFO  
[NIOServerCxn.Factory:33221:nioserverc...@531] - Renewing session 
0x11f55b815b3
[junit] 2009-02-08 11:49:37,353 - INFO  [main:clientb...@300] - STOPPING 
server
[junit] 2009-02-08 11:49:37,353 - INFO  [main:nioserverc...@752] - closing 
session:0x11f55b815b3 NIOServerCnxn: 
java.nio.channels.SocketChannel[connected local=/127.0.0.1:33221 
remote=/127.0.0.1:36682]
[junit] 2009-02-08 11:49:37,354 - WARN  
[main-SendThread:clientcnxn$sendthr...@898] - Exception closing session 
0x11f55b815b3 to sun.nio.ch.selectionkeyi...@dec8b3
[junit] java.io.IOException: Read error rc = -1 
java.nio.DirectByteBuffer[pos=0 lim=4 cap=4]
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:632)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:876)
[junit] 2009-02-08 11:49:37,354 - INFO  
[NIOServerCxn.Factory:33221:nioservercnxn$fact...@176] - NIOServerCnxn factory 
exited run method
[junit] 2009-02-08 11:49:37,355 - INFO  [main:finalrequestproces...@265] - 
shutdown of request processor complete
[junit] 2009-02-08 11:49:37,355 - INFO  
[SyncThread:0:syncrequestproces...@117] - SyncRequestProcessor exited!
[junit] 2009-02-08 11:49:37,355 - INFO  
[ProcessThread:-1:preprequestproces...@111] - PrepRequestProcessor exited loop!
[junit] 2009-02-08 11:49:37,454 - INFO  [main:clientb...@306] - STARTING 
server
[junit] 2009-02-08 11:49:37,455 - INFO  [main:zookeeperser...@156] - 
Created server
[junit] 2009-02-08 11:49:37,456 - INFO  [main:files...@71] - Reading 
snapshot 
http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/ws/trunk/build/test/tmp/test5752499087242004722.junit.dir/version-2/snapshot.3
 
[junit] 2009-02-08 11:49:37,457 - INFO  [main:filetxnsnap...@198] - 
Snapshotting: 5
[junit] 2009-02-08 11:49:37,460 - INFO  
[NIOServerCxn.Factory:33221:nioserverc...@621] - Processing stat command from 
/127.0.0.1:36684
[junit] 2009-02-08 11:49:37,460 - WARN  
[NIOServerCxn.Factory:33221:nioserverc...@417] - Exception causing close of 
session 0x0 due to java.io.IOException: closing
[junit] 2009-02-08 11:49:37,460 - INFO  
[NIOServerCxn.Factory:33221:nioserverc...@752] - closing session:0x0 
NIOServerCnxn: java.nio.channels.SocketChannel[connected 

[jira] Commented: (ZOOKEEPER-276) Bookkeeper contribution

2009-02-08 Thread dhruba borthakur (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671566#action_12671566
 ] 

dhruba borthakur commented on ZOOKEEPER-276:


I have a simple question about bookkeeper ( I could not find  design doc, if 
there is one, please point me to it).

Suppose I have a service with 3 bookies and 1 ledger. I write 1 ledger entry. 
When this appliction-write to the ledger entry is complete, this transaction is 
 successfully done on at least 2 of the bookies. Does the completion of the 
application-write also guarantee that this transaction is synchonously 
persisted on the disk on these two bookies, or does this transaction reside in 
memory of these two bookies and is lazily flushed? Thanks.

> Bookkeeper contribution
> ---
>
> Key: ZOOKEEPER-276
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-276
> Project: Zookeeper
>  Issue Type: New Feature
>Reporter: Luca Telloli
>Assignee: Flavio Paiva Junqueira
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, 
> ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, 
> ZOOKEEPER-276.patch, ZOOKEEPER-276.patch
>
>
> BookKeeper is a system to reliably log streams of records. In BookKeeper, 
> servers are "bookies", log streams are "ledgers", and each unit of a log (aka 
> record) is a "ledger entry". BookKeeper is designed to be reliable; bookies, 
> the servers that store ledgers can be byzantine, which means that some subset 
> of the bookies can fail, corrupt data, discard data, but as long as there are 
> enough correctly behaving servers the service as a whole behaves correctly; 
> the meta data for BookKeeper is stored in ZooKeeper.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.