I tried that and one point I had one table with 6 regions all on the same server. no big deal right now just wanted to know that there was work to be done on it.
Thanks Billy "stack" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hey Billy: > > The region assignment algorithim is kinda basic. For sure needs work but > it works good enough for the time being. I'd say your bad distribution > has to do w/ the low number of regionservers. Try putting a regionserver > on your master machine and see how the distribution is then. > > St.Ack > > > Billy wrote: >> I have a small setup I am running this on its 3 servers a master and >> namenode and the other 2 are datanodes and region servers. >> >> when I restart the services always the regions from one of my tables get >> put all on one server so I have >> >> server 1: Root >> server 2: META, tablepart1,tablepart2,tablepart3,tablepart4 >> >> Vary rare does the table parts get split on to more then one server. >> >> Is there some rule that is happening to place these on different server? >> >> I thank when starting up master and all region server the tables parts >> should be placed in round ribbon fashion then as load is applied table >> parts moved / placed based on load on region servers. >> >> >> >> > >
