Hi,
One of my region server is still listed on the webpage Region Server, but
it raised folloing message while running my program.
10/03/30 13:11:18 INFO ipc.HbaseRPC: Server at /10.81.47.43:60020 could not
be reached after 1 tries, giving up
Any suggestion?
Fleming Chiu(邱宏明)
707-6128
y_823...@t
J-D thanks for your reply. I have some doubts which I posted inline . Kindly
help me
On Tue, Mar 30, 2010 at 2:23 AM, Jean-Daniel Cryans wrote:
> Inline.
>
> J-D
>
> On Mon, Mar 29, 2010 at 11:45 AM, john smith
> wrote:
> > Hi all,
> >
> > I read the issue HBase-57 (
> https://issues.apache.org/
This use case is an ideal one for coprocessors. Alas, the coprocessor feature
is not finished yet.
More inline.
> From: William Kang
> Subject: Re: Questions about data distribution in HBase
>
> What I need is a low latency system can perform some videos
> processes on the fly. For this reason
Hi,
Thanks a lot for your detailed suggestions.
To answer Tim's question, let me elaborate a little bit of the case I am
working on. What I need is a low latency system can perform some videos
processes on the fly. For this reason, a M/R probably won't do the job. The
reason I chose hadoop is bec
Please see inline.
> From: David Swift
>
> Andrew,
>
> The TimeToLive works exactly as you described. It's
> perfect for our needs.
>
> However, I aged out several hundred thousand rows, waited
> about 10 minutes, and then ran a compact from the HBase
> shell. During the whole period, I ran a
William -
If you are processing video files (depending on how big they are), a
better prospect might be to store video files in hdfs only and exploit
hadoop rpc (see - avro) for a custom protocol to process the same. Katta
suggested inline is a great example of that ( custom protocol on top of a
I've posted an overview of ZooKeeper 3.3.0's low level monitoring
commands that you might find useful. A number were added in this release
in response to user requests: http://bit.ly/940Ag1
Regards,
Patrick
Andrew,
The TimeToLive works exactly as you described. It's perfect for our needs.
However, I aged out several hundred thousand rows, waited about 10 minutes,
and then ran a compact from the HBase shell. During the whole period, I ran
a periodic du command on the Hadoop data directory. After
Hi William,
I think you are slightly confused about the usage and intention of HBase.
Let me first say that HBase is a *storage* system designed for low latency,
random access retrieval - built on top of HDFS for high availability. That
is, it's a storage system, not a processing system. It solves
I have got to start paying more attention to this list again :)
On Fri, Mar 26, 2010 at 12:50 PM, Ryan Rawson wrote:
> Looks like we don't use agile json in trunk. I don't think it was
> ever used for much, should be easy to get rid of it in trunk.
>
> On Fri, Mar 26, 2010 at 12:40 PM, Andrew Pu
Inline.
J-D
On Mon, Mar 29, 2010 at 11:45 AM, john smith wrote:
> Hi all,
>
> I read the issue HBase-57 ( https://issues.apache.org/jira/browse/HBASE-57 )
> . I don't really understand the use of assigning regions keeping DFS in
> mind. Can anyone give an example usecase showing its advantages
Hi folks,
I've seen some people around the list that recommend rolling one's own
indexes. Others say to just go with
the org.apache.hadoop.hbase.client.tableindexed package. A quick scan of the
wiki does not reveal any best practices. Presentations from the devs such as
the Oakland ApacheCon slide
Hi all,
I read the issue HBase-57 ( https://issues.apache.org/jira/browse/HBASE-57 )
. I don't really understand the use of assigning regions keeping DFS in
mind. Can anyone give an example usecase showing its advantages . Can
map-reduce exploit it's advantage in any way (if data is distributed in
Andrew,
As long as it cleans up the entire row when all the columns are garbage
collected, that'll be great! I'll experiment with that approach right away.
Thanks!
Andrew Purtell-2 wrote:
>
> Hi David,
>
> What about setting time to lives on column families? You can add or change
> the 'TTL
Hi David,
What about setting time to lives on column families? You can add or change the
'TTL' attribute on a column family in the shell, or specify a time to live when
creating a table. See javadoc for HColumnDescriptor. A time to live is a Long
value (unit is microseconds) associated with the
Hi,
We're evaluating HBase and we have a case where we would want to drop on the
order of about 3 billion of the oldest records out of about 500 billion at
once. We would take measures to ensure that there would be no new inserts
into that old age range during the deletion. We would know the lo
Yes the issue was inside the indexed regionserver: We deleted the old
index row then immediately put-ed the new one
On Mon, Mar 29, 2010 at 10:57 AM, George Stathis wrote:
> That sounds about right. I'm assuming the delete/put index timestamp issue
> lies within the IndexedTable put call and is n
That sounds about right. I'm assuming the delete/put index timestamp issue
lies within the IndexedTable put call and is not related to how the client
makes the call right? I'm asking because we suspected timestamp issues and
we tried to introduce a delay between the initial put and the second one b
We already had an entry in the wiki for this issue but it wasn't super
explicit about what's happening, so I completely rewrote it using the
logs from this thread. See
http://wiki.apache.org/hadoop/Hbase/Troubleshooting#A9
Also I created a jira about putting that link directly into the "We
slept X
On Sun, Mar 28, 2010 at 9:16 PM, steven zhuang
wrote:
> thanks, you guys,
> Actually we have thought of producing some results
> for queries before user does the query, that's an option too, a good one.
> But I still wonna know how powerful HBase can be in this "big table" case.
>
I see
2010-03-28 20:24:27,439 WARN org.apache.hadoop.hbase.util.Sleeper: We slept
79410ms, ten times longer than scheduled
: 5000
2010-03-28 20:24:27,439 WARN org.apache.hadoop.hbase.util.Sleeper: We slept
78781ms, ten times longer than scheduled
: 3000
That means a sleeping thread slept for, in
This was fixed in https://issues.apache.org/jira/browse/HBASE-2174,
will be available in 0.20.4 (or you can patch it on your 0.20.3,
should apply easily).
J-D
On Mon, Mar 29, 2010 at 3:58 AM, Al Lias wrote:
> We have a DNS installation that has a HA-Logic, that may fail for say 10
> seconds.
>
>
Def not the expected behavior and does not sound like user error..
Quick skim looks likk its
https://issues.apache.org/jira/browse/HBASE-2286.
Hbase does not gracefully handle the case where a put after a delete
both have the same millisecond timestamp. Indexing table contrib was
using this patter
Hey folks,
I hope this is just user error but I wanted to see if folks have encountered
this scenario using IndexedTable. We followed the well known by now article
on how to set up secondary indexes (
http://rajeev1982.blogspot.com/2009/06/secondary-indexes-in-hbase.html) .
Works OK on the first t
Hi,
One of our region servers was shut down with the following messages in the
log. It seems like communication with the zookeeper timed out and when it
later reconnected, the session was expired and the region server then shut
itself down. Seem strange to me that it should shut down, why did it n
We have a DNS installation that has a HA-Logic, that may fail for say 10
seconds.
In such a case we experience the following:
* DNS goes down
* The Master gets this: "Received report from unknown server -- telling
it to MSG_CALL_SERVER_STARTUP" (Probably the IP is "unknown")
* The Regionservers d
Hi,
just a guess: maybe it has something to do with it being a "LocalJobRunner"?
Does that even run on the cluster (not using eclipse myself so am not sure).
Greetz,
Vukasin
On Mar 28, 2010, at 21:10 , Something Something wrote:
> When I run a Hadoop job in a command shell it runs in 21 sec
27 matches
Mail list logo
