Closed Bug 630316 Opened 11 years ago Closed 11 years ago

Investigate using max filesize of 2GB for HBase config

Categories

(Mozilla Metrics :: Hadoop/HBase Operations, defect)

HP
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Unreviewed

People

(Reporter: dre, Assigned: tmary)

References

Details

Tweak suggested based on review of the frequency of rollover and the understanding of our data patterns, specifically large blobs stored in the raw_data:dump column and smaller blobs stored in all the other column families.

This is a test that should happen on our secondary cluster first.
Blocks: 630317
Blocks: 630318
No longer depends on: 630305
No longer depends on: 630310
No longer blocks: 630317
No longer depends on: 630314
No longer depends on: 630312
Assignee: nobody → xstevens
No longer blocks: 630318
Depends on: 630312
Assignee: xstevens → tmeyarivan
We should leave the config property at the default and only increase the max filesize for the one table we are concerned with:

> alter 'crash_reports', METHOD => 'table_att', MAX_FILESIZE => '2147483648'
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.