infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15179) minotaur has problems with huge emails
Date Wed, 27 Sep 2017 10:20:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182322#comment-16182322
] 

Daniel Gruno commented on INFRA-15179:
--------------------------------------

The initial import emails should, imho, ideally just be /dev/nulled, as that's an import covered
by whatever SGA is in place..

> minotaur has problems with huge emails
> --------------------------------------
>
>                 Key: INFRA-15179
>                 URL: https://issues.apache.org/jira/browse/INFRA-15179
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>
> It looks like minotaur has a problem archiving very long mail messages.
> The amaterasu-commits archive is missing indices 3 and 6, which are both very long mails
(over 300k lines each).
> [The mails are present on mbox-vm and in the hermes archive.]
> They are automated emails from the ASF dual-hosted git repository.
> However I wonder whether such large mails should be generated?
> If possible it would be better to split them into multiple emails.
> Or only send a summary?
> Note that the mails don't appear on lists.a.o either.
> If such mails cannot be size limited then both minotaur and lists.a.o will need to be
tweaked to allow for them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message