[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4379:
--
Attachment: hadoop-stack-namenode-aa0-000-12.u.powerset.com.log.gz
Namenode log that covers the forever cycle
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721409#action_12721409
]
stack commented on HADOOP-4379:
---
I can manufacture a situation where we're stuck
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714168#action_12714168
]
stack commented on HADOOP-4379:
---
In this test run, the append never succeeds o
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713779#action_12713779
]
stack commented on HADOOP-4379:
---
I tested some more and new reader sees 0 data and get
[
https://issues.apache.org/jira/browse/HADOOP-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713704#action_12713704
]
stack commented on HADOOP-4681:
---
.bq For e.g. it looks like 'a failure' is
[
https://issues.apache.org/jira/browse/HADOOP-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713656#action_12713656
]
stack commented on HADOOP-4681:
---
.bq We could define successful datanode conenctio
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713329#action_12713329
]
stack commented on HADOOP-4379:
---
... and the read finds a zero-length file (nothing
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713316#action_12713316
]
stack commented on HADOOP-4379:
---
After a chat with Hairong and Dhruba, it was thought
[
https://issues.apache.org/jira/browse/HADOOP-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712493#action_12712493
]
stack commented on HADOOP-4681:
---
+1 on patch being applied to TRUNK as well as to 0.20,
Issue Type: Bug
Components: dfs
Affects Versions: 0.19.1, 0.19.0, 0.18.3
Reporter: stack
We've seen this hang rare enough but when it happens it locks up the
application. We've seen it at least in 0.18.x and 0.19.x (we don't have much
experience with
s Versions: 0.20.0, 0.19.1, 0.19.0, 0.18.3
Reporter: stack
We see this frequently in our application, hbase, where dfsclients are held
open across long periods of time. It would seem that any hiccup fetching a
block becomes a permanent black mark and though the serving datanode pas
[
https://issues.apache.org/jira/browse/HADOOP-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710608#action_12710608
]
stack commented on HADOOP-5744:
---
@ Hairong
.bq ..do you still need to recover the l
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710549#action_12710549
]
stack commented on HADOOP-4379:
---
My testing was done with hadoop 0.20.0 (I amended patc
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710546#action_12710546
]
stack commented on HADOOP-4379:
---
v9 works well in basic testing. If I crash the wr
[
https://issues.apache.org/jira/browse/HADOOP-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710541#action_12710541
]
stack commented on HADOOP-5744:
---
@ Hairong
.bq My question is that why the file need
[
https://issues.apache.org/jira/browse/HADOOP-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709961#action_12709961
]
stack commented on HADOOP-5744:
---
Thanks Hairong. Any comment on the unqualified &#
[
https://issues.apache.org/jira/browse/HADOOP-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709612#action_12709612
]
stack commented on HADOOP-5744:
---
A few comments and questions:
Document is without con
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708275#action_12708275
]
stack commented on HADOOP-4379:
---
Tried the patch on loaded cluster. First attempt got
[
https://issues.apache.org/jira/browse/HADOOP-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5797:
--
Attachment: pe.java
Randomize the way we write the splits.
> Better distribution in
Project: Hadoop Core
Issue Type: Bug
Reporter: stack
Assignee: stack
Fix For: 0.20.0
Performance Evaluation when the number of clients was large (and thus number of
rows to input) was clumping so we'd beat up on one box then the next.
--
[
https://issues.apache.org/jira/browse/HADOOP-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701392#action_12701392
]
stack commented on HADOOP-4379:
---
@Dhruba Any luck testing at scale? (Looks like HADOOP-
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674006#action_12674006
]
stack commented on HADOOP-5079:
---
I moved the patch that was added to the reopened issu
[
https://issues.apache.org/jira/browse/HADOOP-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5255:
--
Status: Patch Available (was: Open)
Attached patch works for TRUNK also. Passing to hudson.
> Fix
[
https://issues.apache.org/jira/browse/HADOOP-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5255:
--
Attachment: hadoop-core-hash-2-branch-0.20.patch
Jonathan Ellis patch moved over from HADOOP-5079. Fixes
Issue Type: Bug
Components: io
Affects Versions: 0.20.0, 0.21.0
Reporter: stack
Priority: Minor
Fix For: 0.20.0, 0.21.0
HADOOP-5079 did this "HashFunction.hash restricts initval for the next hash to
the [0, maxValue) range of the hash in
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672157#action_12672157
]
stack commented on HADOOP-5079:
---
I took a look at the patch and confirmed Math
On Thu, Jan 29, 2009 at 4:16 PM, Nigel Daley wrote:
>
> I would like to propose that we apply this same "fix" to sync in 0.19.1 and
> 0.20.0. Since append requires the full semantics of sync, I propose we also
> disable append (perhaps throw UnsupportedOperationException from API?).
> Yes, this
On Tue, Feb 3, 2009 at 7:02 PM, Sanjay Radia wrote:
>
> Many in the team have come to the conclusion that complex projects like
> append should be done on a separate branch in the first place and integrated
> with trunk when the project is stable.
>
How do we determine when a feature on the bra
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3315:
--
Comment: was deleted
> New binary file format
> --
>
> Key:
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3315:
--
Attachment: (was: hfile2.patch)
> New binary file format
> --
>
>
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3315:
--
Attachment: hfile2.patch
More stripping. This patch has HFile sort of working again (Its a hackup with
ugly
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669778#action_12669778
]
stack commented on HADOOP-3315:
---
Thanks Hong. I was talking about fact that '2
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669359#action_12669359
]
stack edited comment on HADOOP-3315 at 2/1/09 1:07 AM:
---
Movin
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3315:
--
Status: In Progress (was: Patch Available)
Moving it to 'resume progress' because of Hong'
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669312#action_12669312
]
stack commented on HADOOP-3315:
---
Digging, looks like ChunkDecoder.close is actually c
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669146#action_12669146
]
stack commented on HADOOP-3315:
---
Here's one issue in TFile that was causing gri
The below proposes pushing a working append out 6 months or so.
Can we have pointers as to what is meant by 'quality issues' in the below so
we can make a more informed vote or is it just the hdfs issue posted against
0.19.1? Is it there also that we would find what is involved making append
work
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668761#action_12668761
]
stack commented on HADOOP-3315:
---
I should add I tested using local filesystem and
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668759#action_12668759
]
stack commented on HADOOP-3315:
---
Thanks for the above especially the bit on concur
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668588#action_12668588
]
stack commented on HADOOP-3315:
---
Hmm. Looking at doing random accesses and it seems li
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668538#action_12668538
]
stack commented on HADOOP-3315:
---
On an alternate BCFile implementation, we're thin
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668271#action_12668271
]
stack commented on HADOOP-3315:
---
I've been playing around w/ the last patch
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668095#action_12668095
]
stack commented on HADOOP-5079:
---
Thanks Raghu. I moved the CHANGES.txt e
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666850#action_12666850
]
stack commented on HADOOP-5079:
---
Committed to 0.20 branch too.
> HashF
[
https://issues.apache.org/jira/browse/HADOOP-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HADOOP-5121:
-
Assignee: stack
> Fix shell usage for format.wi
[
https://issues.apache.org/jira/browse/HADOOP-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HADOOP-5121.
---
Resolution: Fixed
Fix Version/s: 0.20.0
> Fix shell usage for format.wi
Fix shell usage for format.width
Key: HADOOP-5121
URL: https://issues.apache.org/jira/browse/HADOOP-5121
Project: Hadoop Core
Issue Type: Bug
Reporter: stack
--
This message is automatically
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5079:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed (One line change that improves a
HADOOP-5079 has been in patch-submitted state with a few days now and
the few times I've looked, hudson patch queue is empty. Maybe I missed
a flag on the JIRA? Could a kind soul tell me where I went awry?
Thanks,
St.Ack
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5079:
--
Status: In Progress (was: Patch Available)
> HashFunction inadvertently destroys some randomn
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HADOOP-5079:
-
Assignee: stack
> HashFunction inadvertently destroys some randomn
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5079:
--
Status: Patch Available (was: In Progress)
> HashFunction inadvertently destroys some randomn
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5079:
--
Fix Version/s: 0.20.0
Hadoop Flags: [Reviewed]
> HashFunction inadvertently destroys some randomn
[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665247#action_12665247
]
stack commented on HADOOP-5079:
---
Patch looks good to me. Will commit in a day or so un
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663442#action_12663442
]
stack commented on HADOOP-4802:
---
Removed my patches. Write me offline if want to know
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: (was: 4802-v2.patch)
> RPC Server send buffer retains size of largest response ever s
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: (was: 4802-v4-TRUNK.patch)
> RPC Server send buffer retains size of largest response e
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: (was: 4802.patch)
> RPC Server send buffer retains size of largest response ever s
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: (was: 4802-v3.patch)
> RPC Server send buffer retains size of largest response ever s
[
https://issues.apache.org/jira/browse/HADOOP-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HADOOP-5011.
---
Resolution: Invalid
Pardon... wrong component
> Scanner setup takes too l
Scanner setup takes too long...
---
Key: HADOOP-5011
URL: https://issues.apache.org/jira/browse/HADOOP-5011
Project: Hadoop Core
Issue Type: Bug
Reporter: stack
posix4? and dr_ryan are trying to
On Thu, Jan 8, 2009 at 10:39 AM, Doug Cutting wrote:
> So this sort of optimization may only have a significant impact for jobs
> whose maps do not produce much output.
Don't forget the lowly non-MR users of HDFS. The short-circuit looks
promising improving HDFS random access times.
St.Ack
[
https://issues.apache.org/jira/browse/HADOOP-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656875#action_12656875
]
stack commented on HADOOP-4801:
---
Tried installing patch to see what for an improvement
[
https://issues.apache.org/jira/browse/HADOOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HADOOP-3063:
-
Assignee: Andrzej Bialecki
> BloomMapFile - fail-fast version of MapFile for sparsely populated
[
https://issues.apache.org/jira/browse/HADOOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3063:
--
Resolution: Fixed
Fix Version/s: 0.20.0
Release Note: Implements a subclass of MapFile that
[
https://issues.apache.org/jira/browse/HADOOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656360#action_12656360
]
stack commented on HADOOP-3063:
---
The failing tests seem unrelated to this patch:
{
[
https://issues.apache.org/jira/browse/HADOOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656329#action_12656329
]
stack commented on HADOOP-3063:
---
+1 Test now passes locally with v4. Took quick loo
[
https://issues.apache.org/jira/browse/HADOOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655793#action_12655793
]
stack commented on HADOOP-3063:
---
Reviewing the patch, it looks great. The above fai
[
https://issues.apache.org/jira/browse/HADOOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655778#action_12655778
]
stack commented on HADOOP-3063:
---
Andrzej: It failed its own unit test up on hu
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655095#action_12655095
]
stack commented on HADOOP-4802:
---
> It's probably a premature optimization.
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: 4802-v4-TRUNK.patch
Made HBAOS static (Had to move it out of Server#Handler to do so). Removed
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: 4802-v3.patch
v3 removes the unnecessary equality test (Thanks Raghu)
> RPC Server send buf
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654990#action_12654990
]
stack commented on HADOOP-4802:
---
> I'm still not convinced we should do more
[
https://issues.apache.org/jira/browse/HADOOP-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654956#action_12654956
]
stack commented on HADOOP-4797:
---
Raghu: There is one on line #60 ('lager') b
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654951#action_12654951
]
stack commented on HADOOP-4802:
---
Patch applies to 0.19 and to TRUNK.
> RPC Serv
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: 4802-v2.patch
Thanks for the feedback lads.
I like your suggestions Raghu. This patch removes
[
https://issues.apache.org/jira/browse/HADOOP-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654242#action_12654242
]
stack commented on HADOOP-4797:
---
Suggested fix sounds good to me. +1 on patch. W
[
https://issues.apache.org/jira/browse/HADOOP-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-4802:
--
Attachment: 4802.patch
Suggested fix: reset BAOS if larger than N * initial buffer size.
> RPC Server s
: Bug
Components: ipc
Affects Versions: 0.19.0, 0.18.2
Reporter: stack
The stack-based ByteArrayOutputStream in Server.Hander is reset each time
through the run loop. This will set the BAOS 'size' back to zero but the
allocated backing buffer is unaltered. If
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3422:
--
Resolution: Fixed
Fix Version/s: (was: 0.19.1)
(was: hudson)
Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650279#action_12650279
]
stack commented on HADOOP-3422:
---
Thanks for the review Brian.
Unless objection,
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3422:
--
Status: Patch Available (was: In Progress)
Try hudson w/ new version of patch.
> Ganglia counter metr
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3422:
--
Status: In Progress (was: Patch Available)
> Ganglia counter metrics are all reported with the metric n
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HADOOP-3422:
-
Assignee: stack
> Ganglia counter metrics are all reported with the metric name "value&
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-3422:
--
Attachment: ganglia-patch-3422-updated-v2.patch
Version of patch that addresses the above comments (Uses
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649534#action_12649534
]
stack commented on HADOOP-3422:
---
I agree the test failure is unrelated but would lik
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649458#action_12649458
]
stack commented on HADOOP-3315:
---
Thanks for update Hong. If you get a minute, yeah,
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648700#action_12648700
]
stack commented on HADOOP-3422:
---
Couple of nitpicks: Use StringBuilder instea
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647714#action_12647714
]
stack commented on HADOOP-3315:
---
Hows it going lads? Any update? Do you think TFile
[
https://issues.apache.org/jira/browse/HADOOP-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HADOOP-4562.
---
Resolution: Duplicate
Thanks. I confirmed that the debug message no longer shows (My bad, HBase was
using
[
https://issues.apache.org/jira/browse/HADOOP-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644405#action_12644405
]
stack commented on HADOOP-4499:
---
Is this supposed to have fixed HADOOP-4562?
> DF
[
https://issues.apache.org/jira/browse/HADOOP-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644404#action_12644404
]
stack commented on HADOOP-4562:
---
I'm running with r709534 so HADOOP-4499 is in pl
Project: Hadoop Core
Issue Type: Bug
Components: dfs
Affects Versions: 0.19.0
Reporter: stack
Priority: Blocker
Updating hbase to use 0.19.0RC0 or latest from branch-0.19, I see reams of this
in logs:
{code}
2008-10-31 18:33:4
+1
- I took a run through the documentation and the UIs
- Ran hbase unit tests and load test
St.Ack
Nigel Daley wrote:
I have created a candidate build for Hadoop 0.18.2. This fixes 25
issues in 0.18.1.
*** Please download and test it before the
*** vote closes on Monday, November 3.
htt
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638717#action_12638717
]
stack commented on HADOOP-3422:
---
Good stuff Brian.
1). Just by way of FYI,
[
https://issues.apache.org/jira/browse/HADOOP-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638491#action_12638491
]
stack commented on HADOOP-3422:
---
I took a look at the patch. You have this in a few pl
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636455#action_12636455
]
stack commented on HADOOP-3315:
---
@Hong
So, to read a random key, I'd now d
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634322#action_12634322
]
stack commented on HADOOP-3315:
---
bq. ...would your auxiilary index remember how
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634262#action_12634262
]
stack commented on HADOOP-3315:
---
To Owen's list I'd suggest adding amenable
[
https://issues.apache.org/jira/browse/HADOOP-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634028#action_12634028
]
stack commented on HADOOP-3315:
---
@Hong. Yeah. You got all my questions. Here&#x
1 - 100 of 274 matches
Mail list logo
