sorry Doug, i'm not in office now.i am at another city. i send you the outputs on monday morning. thank you very much Bye Hatice 12 Mayıs 2013 Pazar tarihinde Doug Judd adlı kullanıcı şöyle yazdı:
> I think I figured out what's going on. It looks like rs1, the range > server being recovered, contains a range for table '3/4' which has been > dropped, which is causing the recovery to fail. Clearly this range should > have been dropped when the table was dropped. I've filed issue > 1069<https://code.google.com/p/hypertable/issues/detail?id=1069>to resolve > this problem. In the meantime, I can fix your MML to purge this > bad range so that you can get your database back up and running. I will do > this on Monday and send you instructions on how to resolve the problem. > But please follow the instructions from my previous e-mail. However, you > only need to dump the rsml for rs1: > > /opt/hypertable/doug/current/bin/ht metalog_dump > /hypertable/servers/rs1/log/rsml > > - Doug > > > On Sat, May 11, 2013 at 9:59 AM, Doug Judd <[email protected]> wrote: > > Hi Hatice, > > There is one more thing that I'd like you to do. Please do the following > and send me the output: > > 1. Stop hypertable (cap stop) > > 2. One the master machine, start the DFS broker: > > /opt/hypertable/current/bin/start-dfsbroker.sh hadoop > > 3. Run the following command, change the "6" in the below command to match > the largest range server in your setup (you can figure it out by running > hadoop > fs -ls /hypertable/servers. > > for ((i=1; i<=6; i++)); do echo "rs$i"; > /opt/hypertable/doug/current/bin/ht metalog_dump > /hypertable/servers/rs$i/log/rsml; echo ""; done > > 4. Send me the output of the above command. > > - Doug > > P.S. Leave Hypertable stopped until I get back to you.. > > > > On Sat, May 11, 2013 at 2:40 AM, Hatice Çobanoğlu < > [email protected]> wrote: > > hi Doug, > i work with mehmet ali. i send you this file in attach. > > bye > Hatice > > > > > 2013/5/11 Doug Judd <[email protected]> > > Also, please run the Hyperspace shell as follows: > > /opt/hypertable/current/bin/ht hyperspace > > and run the following command: > > hyperspace> dump / "~/hsdump.txt"; > > and send me the ~/hsdump.txt file. > > - Doug > > > On Thu, May 9, 2013 at 11:59 PM, Doug Judd <[email protected]> wrote: > > Ok, then run "grep ERROR Hypertable.Master.log" and send me the output. > > - Doug > > > > On Thu, May 9, 2013 at 11:45 PM, Mehmet Ali Cetinkaya < > [email protected]> wrote: > > i see Doug, but master log is very huge (4.9 gb) and i used "tail -f" > command but if it is not enough i will make try tar or maybe split and send > to you last part of master.log ok? > > tail -f Hypertable.Master.log > 1368097650 INFO Hypertable.Master : > (/root/src/hypertable/src/cc/Hypertable/Master/OperationRecoverRanges.cc:225) > Leaving RecoverServerRanges rs1 plan_generation=1 type=3 state=PHANTOM_LOAD > > -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hypertable-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
