You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bookkeeper.apache.org by Savitha Devi Inbasekaran <Sa...@smartek21.com> on 2013/01/25 12:36:11 UTC

Not able to start the bookkeeper

Hi,
Following are the steps which I followed to install bookkeeper and start the same.


*         Downloaded the bookkeeper version 4.2.1 from the link http://apache.techartifact.com/mirror/zookeeper/bookkeeper/ .

*         Set the configuration parameter in bookkeeper-server/conf/bk_server.conf as follows:

*             bookiePort, Port number that the bookie listens on;

*             zkServers, Comma separated list of ZooKeeper servers with a hostname:port format;

*             journalDir, Path for Log Device (stores bookie write-ahead log);

*             ledgerDir, Path for Ledger Device (stores ledger entries);

*         Created /ledgers & /ledgers/available in zookeeper before running the cluster. By using the below

*         bin/bookkeeper org.apache.zookeeper.ZooKeeperMain -server localhost:2181 create /ledgers 0

*         bin/bookkeeper org.apache.zookeeper.ZooKeeperMain -server localhost:2181 create /ledgers/available 0

*         Started zookeeper

*         Run the following command to start the bookie:

*         bin/bookkeeper bookie
But after starting the bookie the below error was observed.

2013-01-25 17:01:55,747 - WARN  - [main:Bookie@493] - INSTANCEID not exists in zookeeper. Not considering it for data verification
2013-01-25 17:01:56,397 - ERROR - [main:Bookie@447] - Cookie exists in zookeeper, but not in all local directories.  Directories missing cookie file are [/tmp/bk-txn/current, /tmp/bk-data/current]
2013-01-25 17:01:56,408 - ERROR - [main:BookieServer@375] - Exception running bookie server :
org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:
                at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:449)
                at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:524)
                at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:96)
                at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:86)
                at org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:361)
any help could be appreciated. Thanks in advance.

Thanks,
Savitha

FW: Not able to start the bookkeeper

Posted by Uma Maheswara Rao G <ma...@huawei.com>.
Looks like your Zookeeper already has Cookie information and starting the Bookie with fresh local directories configured?

Clean the ZK data and try once. or Use Bookkeeper format command: $bookkeeper shell metaformat



Regards,

Uma

________________________________
From: Savitha Devi Inbasekaran [Savithadi@smartek21.com]
Sent: Friday, January 25, 2013 5:06 PM
To: bookkeeper-user@zookeeper.apache.org
Subject: Not able to start the bookkeeper

Hi,
Following are the steps which I followed to install bookkeeper and start the same.


*         Downloaded the bookkeeper version 4.2.1 from the link http://apache.techartifact.com/mirror/zookeeper/bookkeeper/ .

*         Set the configuration parameter in bookkeeper-server/conf/bk_server.conf as follows:

*             bookiePort, Port number that the bookie listens on;

*             zkServers, Comma separated list of ZooKeeper servers with a hostname:port format;

*             journalDir, Path for Log Device (stores bookie write-ahead log);

*             ledgerDir, Path for Ledger Device (stores ledger entries);

*         Created /ledgers & /ledgers/available in zookeeper before running the cluster. By using the below

*         bin/bookkeeper org.apache.zookeeper.ZooKeeperMain -server localhost:2181 create /ledgers 0

*         bin/bookkeeper org.apache.zookeeper.ZooKeeperMain -server localhost:2181 create /ledgers/available 0

*         Started zookeeper

*         Run the following command to start the bookie:

*         bin/bookkeeper bookie
But after starting the bookie the below error was observed.

2013-01-25 17:01:55,747 - WARN  - [main:Bookie@493] - INSTANCEID not exists in zookeeper. Not considering it for data verification
2013-01-25 17:01:56,397 - ERROR - [main:Bookie@447] - Cookie exists in zookeeper, but not in all local directories.  Directories missing cookie file are [/tmp/bk-txn/current, /tmp/bk-data/current]
2013-01-25 17:01:56,408 - ERROR - [main:BookieServer@375] - Exception running bookie server :
org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:
                at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:449)
                at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:524)
                at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:96)
                at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:86)
                at org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:361)
any help could be appreciated. Thanks in advance.

Thanks,
Savitha

RE: Not able to start the bookkeeper

Posted by Uma Maheswara Rao G <ma...@huawei.com>.
Cool!  Happy to hear this :-)

Regards,
Uma

________________________________________
From: Savitha Devi Inbasekaran [Savithadi@smartek21.com]
Sent: Tuesday, January 29, 2013 12:21 PM
To: bookkeeper-user@zookeeper.apache.org
Subject: RE: Not able to start the bookkeeper

Hi Uma,
Thanks. My bookkeeper is running.
Thanks,
Savitha

-----Original Message-----
From: Uma Maheswara Rao G [mailto:maheswara@huawei.com]
Sent: Monday, January 28, 2013 1:01 PM
To: bookkeeper-user@zookeeper.apache.org
Subject: RE: Not able to start the bookkeeper

Hi Savitha,

 Looks like, your configured directories are not having disk space /tmp/bk-data/current Please check and make some available space and try.

Regards,
Uma

________________________________________
From: Savitha Devi Inbasekaran [Savithadi@smartek21.com]
Sent: Monday, January 28, 2013 12:56 PM
To: bookkeeper-user@zookeeper.apache.org
Subject: RE: Not able to start the bookkeeper

Thanks Ivan. After formatting and starting the bookkeeper I got the following error

2013-01-28 12:54:22,856 - ERROR - [main:Journal$LastLogMark@177] - Problems reading from /tmp/bk-data/current/lastMark (this is okay if it is the first time starting this bookie
2013-01-28 12:54:22,937 - WARN  - [Thread-1:LedgerDirsManager@98] - /tmp/bk-data/current is out of space. Adding it to filled dirs list
2013-01-28 12:54:22,978 - INFO  - [BookieJournal-3181:JournalChannel@66] - Opening journal /tmp/bk-txn/current/779148.txn
2013-01-28 12:54:23,046 - INFO  - [main:BookieServer@370] - Register shutdown hook successfully
2013-01-28 12:54:32,952 - ERROR - [Thread-1:LedgerDirsManager@79] - All ledger directories are non writable
org.apache.bookkeeper.bookie.LedgerDirsManager$NoWritableLedgerDirException: All ledger directories are non writable
        at org.apache.bookkeeper.bookie.LedgerDirsManager.getWritableLedgerDirs(LedgerDirsManager.java:77)
        at org.apache.bookkeeper.bookie.LedgerDirsManager$LedgerDirsMonitor.run(LedgerDirsManager.java:188)
2013-01-28 12:54:32,956 - WARN  - [Thread-1:Bookie@791] - ReadOnly mode is not enabled. Can be enabled by configuring 'readOnlyModeEnabled=true' in configuration.Shutting down bookie
2013-01-28 12:54:32,980 - INFO  - [main-EventThread:ClientCnxn$EventThread@511] - EventThread shut down
2013-01-28 12:54:32,994 - INFO  - [Thread-3:ZooKeeper@679] - Session: 0x13c7f9e7ea20008 closed
2013-01-28 12:54:32,998 - WARN  - [BookieJournal-3181:Journal@549] - Journal exits when shutting down java.lang.InterruptedException
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2052)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
        at org.apache.bookkeeper.bookie.Journal.run(Journal.java:497)
2013-01-28 12:54:33,041 - INFO  - [NIOServerFactory-3181:NIOServerFactory@162] - NIOServerCnxn factory exitedloop.
2013-01-28 12:54:33,043 - INFO  - [Thread-2:BookieServer$1@367] - Shut down bookie server successful

Please help me
Thanks,
Savitha

-----Original Message-----
From: Ivan Kelly [mailto:ivank@apache.org]
Sent: Saturday, January 26, 2013 4:11 AM
To: bookkeeper-user@zookeeper.apache.org
Subject: Re: Not able to start the bookkeeper

Hi Savitha,
>
> 2013-01-25 17:01:55,747 - WARN  - [main:Bookie@493] - INSTANCEID not
> exists in zookeeper. Not considering it for data verification
> 2013-01-25 17:01:56,397 - ERROR - [main:Bookie@447] - Cookie exists in
> zookeeper, but not in all local directories.  Directories missing
> cookie file are [/tmp/bk-txn/current, /tmp/bk-data/current]
> 2013-01-25 17:01:56,408 - ERROR - [main:BookieServer@375] - Exception running bookie server :
> org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:
>                 at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:449)
>                 at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:524)
>                 at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:96)
>                 at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:86)
>                 at
> org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:361)

Have you had a previous bookkeeper install? The error means that the bookie configuration has changed since an previous instance of the bookie. We don't allow the journalDir,ledgerDir or bookiePort to change for a bookie, as this could cause data to silently disappear.

If this is a fresh setup, try formatting. Look at the formatting section on http://zookeeper.apache.org/bookkeeper/docs/r4.2.0/bookkeeperConfig.html

-Ivan

RE: Not able to start the bookkeeper

Posted by Savitha Devi Inbasekaran <Sa...@smartek21.com>.
Hi Uma,
Thanks. My bookkeeper is running.
Thanks,
Savitha

-----Original Message-----
From: Uma Maheswara Rao G [mailto:maheswara@huawei.com] 
Sent: Monday, January 28, 2013 1:01 PM
To: bookkeeper-user@zookeeper.apache.org
Subject: RE: Not able to start the bookkeeper

Hi Savitha,

 Looks like, your configured directories are not having disk space /tmp/bk-data/current Please check and make some available space and try.

Regards,
Uma

________________________________________
From: Savitha Devi Inbasekaran [Savithadi@smartek21.com]
Sent: Monday, January 28, 2013 12:56 PM
To: bookkeeper-user@zookeeper.apache.org
Subject: RE: Not able to start the bookkeeper

Thanks Ivan. After formatting and starting the bookkeeper I got the following error

2013-01-28 12:54:22,856 - ERROR - [main:Journal$LastLogMark@177] - Problems reading from /tmp/bk-data/current/lastMark (this is okay if it is the first time starting this bookie
2013-01-28 12:54:22,937 - WARN  - [Thread-1:LedgerDirsManager@98] - /tmp/bk-data/current is out of space. Adding it to filled dirs list
2013-01-28 12:54:22,978 - INFO  - [BookieJournal-3181:JournalChannel@66] - Opening journal /tmp/bk-txn/current/779148.txn
2013-01-28 12:54:23,046 - INFO  - [main:BookieServer@370] - Register shutdown hook successfully
2013-01-28 12:54:32,952 - ERROR - [Thread-1:LedgerDirsManager@79] - All ledger directories are non writable
org.apache.bookkeeper.bookie.LedgerDirsManager$NoWritableLedgerDirException: All ledger directories are non writable
        at org.apache.bookkeeper.bookie.LedgerDirsManager.getWritableLedgerDirs(LedgerDirsManager.java:77)
        at org.apache.bookkeeper.bookie.LedgerDirsManager$LedgerDirsMonitor.run(LedgerDirsManager.java:188)
2013-01-28 12:54:32,956 - WARN  - [Thread-1:Bookie@791] - ReadOnly mode is not enabled. Can be enabled by configuring 'readOnlyModeEnabled=true' in configuration.Shutting down bookie
2013-01-28 12:54:32,980 - INFO  - [main-EventThread:ClientCnxn$EventThread@511] - EventThread shut down
2013-01-28 12:54:32,994 - INFO  - [Thread-3:ZooKeeper@679] - Session: 0x13c7f9e7ea20008 closed
2013-01-28 12:54:32,998 - WARN  - [BookieJournal-3181:Journal@549] - Journal exits when shutting down java.lang.InterruptedException
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2052)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
        at org.apache.bookkeeper.bookie.Journal.run(Journal.java:497)
2013-01-28 12:54:33,041 - INFO  - [NIOServerFactory-3181:NIOServerFactory@162] - NIOServerCnxn factory exitedloop.
2013-01-28 12:54:33,043 - INFO  - [Thread-2:BookieServer$1@367] - Shut down bookie server successful

Please help me
Thanks,
Savitha

-----Original Message-----
From: Ivan Kelly [mailto:ivank@apache.org]
Sent: Saturday, January 26, 2013 4:11 AM
To: bookkeeper-user@zookeeper.apache.org
Subject: Re: Not able to start the bookkeeper

Hi Savitha,
>
> 2013-01-25 17:01:55,747 - WARN  - [main:Bookie@493] - INSTANCEID not 
> exists in zookeeper. Not considering it for data verification
> 2013-01-25 17:01:56,397 - ERROR - [main:Bookie@447] - Cookie exists in 
> zookeeper, but not in all local directories.  Directories missing 
> cookie file are [/tmp/bk-txn/current, /tmp/bk-data/current]
> 2013-01-25 17:01:56,408 - ERROR - [main:BookieServer@375] - Exception running bookie server :
> org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:
>                 at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:449)
>                 at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:524)
>                 at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:96)
>                 at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:86)
>                 at
> org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:361)

Have you had a previous bookkeeper install? The error means that the bookie configuration has changed since an previous instance of the bookie. We don't allow the journalDir,ledgerDir or bookiePort to change for a bookie, as this could cause data to silently disappear.

If this is a fresh setup, try formatting. Look at the formatting section on http://zookeeper.apache.org/bookkeeper/docs/r4.2.0/bookkeeperConfig.html

-Ivan

RE: Not able to start the bookkeeper

Posted by Uma Maheswara Rao G <ma...@huawei.com>.
Hi Savitha,

 Looks like, your configured directories are not having disk space /tmp/bk-data/current 
Please check and make some available space and try.

Regards,
Uma

________________________________________
From: Savitha Devi Inbasekaran [Savithadi@smartek21.com]
Sent: Monday, January 28, 2013 12:56 PM
To: bookkeeper-user@zookeeper.apache.org
Subject: RE: Not able to start the bookkeeper

Thanks Ivan. After formatting and starting the bookkeeper I got the following error

2013-01-28 12:54:22,856 - ERROR - [main:Journal$LastLogMark@177] - Problems reading from /tmp/bk-data/current/lastMark (this is okay if it is the first time starting this bookie
2013-01-28 12:54:22,937 - WARN  - [Thread-1:LedgerDirsManager@98] - /tmp/bk-data/current is out of space. Adding it to filled dirs list
2013-01-28 12:54:22,978 - INFO  - [BookieJournal-3181:JournalChannel@66] - Opening journal /tmp/bk-txn/current/779148.txn
2013-01-28 12:54:23,046 - INFO  - [main:BookieServer@370] - Register shutdown hook successfully
2013-01-28 12:54:32,952 - ERROR - [Thread-1:LedgerDirsManager@79] - All ledger directories are non writable
org.apache.bookkeeper.bookie.LedgerDirsManager$NoWritableLedgerDirException: All ledger directories are non writable
        at org.apache.bookkeeper.bookie.LedgerDirsManager.getWritableLedgerDirs(LedgerDirsManager.java:77)
        at org.apache.bookkeeper.bookie.LedgerDirsManager$LedgerDirsMonitor.run(LedgerDirsManager.java:188)
2013-01-28 12:54:32,956 - WARN  - [Thread-1:Bookie@791] - ReadOnly mode is not enabled. Can be enabled by configuring 'readOnlyModeEnabled=true' in configuration.Shutting down bookie
2013-01-28 12:54:32,980 - INFO  - [main-EventThread:ClientCnxn$EventThread@511] - EventThread shut down
2013-01-28 12:54:32,994 - INFO  - [Thread-3:ZooKeeper@679] - Session: 0x13c7f9e7ea20008 closed
2013-01-28 12:54:32,998 - WARN  - [BookieJournal-3181:Journal@549] - Journal exits when shutting down
java.lang.InterruptedException
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2052)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
        at org.apache.bookkeeper.bookie.Journal.run(Journal.java:497)
2013-01-28 12:54:33,041 - INFO  - [NIOServerFactory-3181:NIOServerFactory@162] - NIOServerCnxn factory exitedloop.
2013-01-28 12:54:33,043 - INFO  - [Thread-2:BookieServer$1@367] - Shut down bookie server successful

Please help me
Thanks,
Savitha

-----Original Message-----
From: Ivan Kelly [mailto:ivank@apache.org]
Sent: Saturday, January 26, 2013 4:11 AM
To: bookkeeper-user@zookeeper.apache.org
Subject: Re: Not able to start the bookkeeper

Hi Savitha,
>
> 2013-01-25 17:01:55,747 - WARN  - [main:Bookie@493] - INSTANCEID not
> exists in zookeeper. Not considering it for data verification
> 2013-01-25 17:01:56,397 - ERROR - [main:Bookie@447] - Cookie exists in
> zookeeper, but not in all local directories.  Directories missing
> cookie file are [/tmp/bk-txn/current, /tmp/bk-data/current]
> 2013-01-25 17:01:56,408 - ERROR - [main:BookieServer@375] - Exception running bookie server :
> org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:
>                 at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:449)
>                 at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:524)
>                 at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:96)
>                 at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:86)
>                 at
> org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:361)

Have you had a previous bookkeeper install? The error means that the bookie configuration has changed since an previous instance of the bookie. We don't allow the journalDir,ledgerDir or bookiePort to change for a bookie, as this could cause data to silently disappear.

If this is a fresh setup, try formatting. Look at the formatting section on http://zookeeper.apache.org/bookkeeper/docs/r4.2.0/bookkeeperConfig.html

-Ivan

RE: Not able to start the bookkeeper

Posted by Savitha Devi Inbasekaran <Sa...@smartek21.com>.
Thanks Ivan. After formatting and starting the bookkeeper I got the following error

2013-01-28 12:54:22,856 - ERROR - [main:Journal$LastLogMark@177] - Problems reading from /tmp/bk-data/current/lastMark (this is okay if it is the first time starting this bookie
2013-01-28 12:54:22,937 - WARN  - [Thread-1:LedgerDirsManager@98] - /tmp/bk-data/current is out of space. Adding it to filled dirs list
2013-01-28 12:54:22,978 - INFO  - [BookieJournal-3181:JournalChannel@66] - Opening journal /tmp/bk-txn/current/779148.txn
2013-01-28 12:54:23,046 - INFO  - [main:BookieServer@370] - Register shutdown hook successfully
2013-01-28 12:54:32,952 - ERROR - [Thread-1:LedgerDirsManager@79] - All ledger directories are non writable
org.apache.bookkeeper.bookie.LedgerDirsManager$NoWritableLedgerDirException: All ledger directories are non writable
	at org.apache.bookkeeper.bookie.LedgerDirsManager.getWritableLedgerDirs(LedgerDirsManager.java:77)
	at org.apache.bookkeeper.bookie.LedgerDirsManager$LedgerDirsMonitor.run(LedgerDirsManager.java:188)
2013-01-28 12:54:32,956 - WARN  - [Thread-1:Bookie@791] - ReadOnly mode is not enabled. Can be enabled by configuring 'readOnlyModeEnabled=true' in configuration.Shutting down bookie
2013-01-28 12:54:32,980 - INFO  - [main-EventThread:ClientCnxn$EventThread@511] - EventThread shut down
2013-01-28 12:54:32,994 - INFO  - [Thread-3:ZooKeeper@679] - Session: 0x13c7f9e7ea20008 closed
2013-01-28 12:54:32,998 - WARN  - [BookieJournal-3181:Journal@549] - Journal exits when shutting down
java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2052)
	at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
	at org.apache.bookkeeper.bookie.Journal.run(Journal.java:497)
2013-01-28 12:54:33,041 - INFO  - [NIOServerFactory-3181:NIOServerFactory@162] - NIOServerCnxn factory exitedloop.
2013-01-28 12:54:33,043 - INFO  - [Thread-2:BookieServer$1@367] - Shut down bookie server successful

Please help me
Thanks,
Savitha

-----Original Message-----
From: Ivan Kelly [mailto:ivank@apache.org] 
Sent: Saturday, January 26, 2013 4:11 AM
To: bookkeeper-user@zookeeper.apache.org
Subject: Re: Not able to start the bookkeeper

Hi Savitha,
> 
> 2013-01-25 17:01:55,747 - WARN  - [main:Bookie@493] - INSTANCEID not 
> exists in zookeeper. Not considering it for data verification
> 2013-01-25 17:01:56,397 - ERROR - [main:Bookie@447] - Cookie exists in 
> zookeeper, but not in all local directories.  Directories missing 
> cookie file are [/tmp/bk-txn/current, /tmp/bk-data/current]
> 2013-01-25 17:01:56,408 - ERROR - [main:BookieServer@375] - Exception running bookie server :
> org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:
>                 at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:449)
>                 at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:524)
>                 at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:96)
>                 at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:86)
>                 at 
> org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:361)

Have you had a previous bookkeeper install? The error means that the bookie configuration has changed since an previous instance of the bookie. We don't allow the journalDir,ledgerDir or bookiePort to change for a bookie, as this could cause data to silently disappear.

If this is a fresh setup, try formatting. Look at the formatting section on http://zookeeper.apache.org/bookkeeper/docs/r4.2.0/bookkeeperConfig.html

-Ivan

Re: Not able to start the bookkeeper

Posted by Ivan Kelly <iv...@apache.org>.
Hi Savitha,
> 
> 2013-01-25 17:01:55,747 - WARN  - [main:Bookie@493] - INSTANCEID not exists in zookeeper. Not considering it for data verification
> 2013-01-25 17:01:56,397 - ERROR - [main:Bookie@447] - Cookie exists in zookeeper, but not in all local directories.  Directories missing cookie file are [/tmp/bk-txn/current, /tmp/bk-data/current]
> 2013-01-25 17:01:56,408 - ERROR - [main:BookieServer@375] - Exception running bookie server :
> org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:
>                 at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:449)
>                 at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:524)
>                 at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:96)
>                 at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:86)
>                 at org.apache.bookkeeper.proto.BookieServer.main(BookieServer.java:361)

Have you had a previous bookkeeper install? The error means that the
bookie configuration has changed since an previous instance of the
bookie. We don't allow the journalDir,ledgerDir or bookiePort to
change for a bookie, as this could cause data to silently disappear.

If this is a fresh setup, try formatting. Look at the formatting
section on
http://zookeeper.apache.org/bookkeeper/docs/r4.2.0/bookkeeperConfig.html

-Ivan