Right now on stage: * collector is storing in both S3 and HBase * processor is using S3 as crash source ** storing processed crash in both S3 and HBase Initially we're going to run production like this, except with HBase as the crash source. Let's put stage in this mode just to make extra sure that it works.
Created attachment 8533620 [details] [diff] [review] bug1108974.diff I think this is all we need. If this looks ok, please feel free to check in. After it goes live, you could test it using submitter and the test crash that's checked into the socorro repo: workon socorro # or otherwise activate virtualenv socorro submitter -u https://crash-reports.allizom.org/submit -s ./testcrash/raw/
Assignee: nobody → rhelmer
Status: NEW → ASSIGNED
Attachment #8533620 - Flags: review?(dmaher)
Created attachment 8533621 [details] [diff] [review] bug1108974.diff Change the benchmark tag too (we have benchmarking turned on for all reads/writes right now)
Attachment #8533621 - Flags: review?(dmaher) → review?(lars)
Comment on attachment 8533621 [details] [diff] [review] bug1108974.diff Pretty straightforward.
Sending processor.ini Transmitting file data . Committed revision 97968.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.