accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-2441) Document internal state stored in RFile names
Date Fri, 07 Mar 2014 21:53:43 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Busbey updated ACCUMULO-2441:
----------------------------------

    Description: 
A recent conversation on #Accumulo pointed out a need for better documentation on how we store
state in RFile names

{noformat}
15:18 < vines_> What are the prefix for files?
15:18 < vines_> A is a full compaction, F is a partial major compaction, I is an import..
uhhh?
15:20 < vines_> oops, F is minor, M is merging
15:20 < elserj> C was manual compact i think?
15:20 < vines_> I thought C was full
15:21 < elserj> you just said A was full
15:21 < vines_> I'm not sure
15:21 < elserj> lol
15:21 < vines_> considering I just contradicted myselkf on F
15:21 < elserj> i thought A was automatic compact and C was user-issued compact
15:21 < elserj> F was a flush, I thought
15:22 < vines_> I don't think we differentiate user interfaced or not
15:22 < vines_> C is a complete compaction - all files
15:22 < vines_> A is an incomplete major compaction
15:22 < vines_> F is a minor compaction
15:22 < vines_> M is a merging minor
15:22 < vines_> alright
15:22 < elserj> ah ok. you'd typically see the C is a user did a compact in the shell
15:22 < elserj> unless you set your ratio to something dumb?
15:23 < elserj> that's probably what i was thinking of
15:33 < vines_> perhaps
15:43 < madrob> A is all.
15:43 < madrob> C is partial
15:43 < madrob> F is flush
15:49 < busbey> could someone file a Jira to document this?
15:49 < busbey> nevermind, I'll do it. ;)
{noformat}

I'm not sure where the correct place for this is. I'm guessing somewhere in javadocs. Maybe
in an advanced section of the administration manual?

  was:
A recent conversation on #Accumulo pointed out a need for better documentation on how we store
state in RFile names

{noformat}
15:18 < vines_> What are the prefix for files?
15:18 < vines_> A is a full compaction, F is a partial major compaction, I is an import..
uhhh?
15:20 < vines_> oops, F is minor, M is merging
15:20 < elserj> C was manual compact i think?
15:20 < vines_> I thought C was full
15:21 < elserj> you just said A was full
15:21 < vines_> I'm not sure
15:21 < elserj> lol
15:21 < vines_> considering I just contradicted myselkf on F
15:21 < elserj> i thought A was automatic compact and C was user-issued compact
15:21 < elserj> F was a flush, I thought
15:22 < vines_> I don't think we differentiate user interfaced or not
15:22 < vines_> C is a complete compaction - all files
15:22 < vines_> A is an incomplete major compaction
15:22 < vines_> F is a minor compaction
15:22 < vines_> M is a merging minor
15:22 < vines_> alright
15:22 < elserj> ah ok. you'd typically see the C is a user did a compact in the shell
15:22 < elserj> unless you set your ratio to something dumb?
15:23 < elserj> that's probably what i was thinking of
15:26 -!- ericnewton_ [~ecnewt2-l@pool-96-244-143-107.bltmmd.fios.verizon.net] has quit [Remote
host closed the connection]
15:33 < vines_> perhaps
15:40 -!- jmhsieh [~jmhsieh@65.50.196.130] has quit [Ping timeout: 264 seconds]
15:43 < madrob> A is all.
15:43 < madrob> C is partial
15:43 < madrob> F is flush
15:49 < busbey> could someone file a Jira to document this?
15:49 < busbey> nevermind, I'll do it. ;)
{noformat}

I'm not sure where the correct place for this is. I'm guessing somewhere in javadocs. Maybe
in an advanced section of the administration manual?


> Document internal state stored in RFile names
> ---------------------------------------------
>
>                 Key: ACCUMULO-2441
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2441
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Sean Busbey
>             Fix For: 1.4.6, 1.5.2, 1.6.1
>
>
> A recent conversation on #Accumulo pointed out a need for better documentation on how
we store state in RFile names
> {noformat}
> 15:18 < vines_> What are the prefix for files?
> 15:18 < vines_> A is a full compaction, F is a partial major compaction, I is an
import.. uhhh?
> 15:20 < vines_> oops, F is minor, M is merging
> 15:20 < elserj> C was manual compact i think?
> 15:20 < vines_> I thought C was full
> 15:21 < elserj> you just said A was full
> 15:21 < vines_> I'm not sure
> 15:21 < elserj> lol
> 15:21 < vines_> considering I just contradicted myselkf on F
> 15:21 < elserj> i thought A was automatic compact and C was user-issued compact
> 15:21 < elserj> F was a flush, I thought
> 15:22 < vines_> I don't think we differentiate user interfaced or not
> 15:22 < vines_> C is a complete compaction - all files
> 15:22 < vines_> A is an incomplete major compaction
> 15:22 < vines_> F is a minor compaction
> 15:22 < vines_> M is a merging minor
> 15:22 < vines_> alright
> 15:22 < elserj> ah ok. you'd typically see the C is a user did a compact in the
shell
> 15:22 < elserj> unless you set your ratio to something dumb?
> 15:23 < elserj> that's probably what i was thinking of
> 15:33 < vines_> perhaps
> 15:43 < madrob> A is all.
> 15:43 < madrob> C is partial
> 15:43 < madrob> F is flush
> 15:49 < busbey> could someone file a Jira to document this?
> 15:49 < busbey> nevermind, I'll do it. ;)
> {noformat}
> I'm not sure where the correct place for this is. I'm guessing somewhere in javadocs.
Maybe in an advanced section of the administration manual?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message