Ayush Saxena created HADOOP-17558:
-
Summary: DistCp: Reduce memory usage using a fixed size
ThreadPoolExecutor
Key: HADOOP-17558
URL: https://issues.apache.org/jira/browse/HADOOP-17558
Project:
[
https://issues.apache.org/jira/browse/HADOOP-17531?focusedWorklogId=559843=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559843
]
ASF GitHub Bot logged work on HADOOP-17531:
---
Author: ASF GitHub Bot
jojochuang commented on a change in pull request #2732:
URL: https://github.com/apache/hadoop/pull/2732#discussion_r585324372
##
File path: hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm
##
@@ -362,6 +362,7 @@ Command Line Options
| `-copybuffersize ` | Size of the
[
https://issues.apache.org/jira/browse/HADOOP-17531?focusedWorklogId=559842=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559842
]
ASF GitHub Bot logged work on HADOOP-17531:
---
Author: ASF GitHub Bot
jojochuang commented on a change in pull request #2732:
URL: https://github.com/apache/hadoop/pull/2732#discussion_r585324372
##
File path: hadoop-tools/hadoop-distcp/src/site/markdown/DistCp.md.vm
##
@@ -362,6 +362,7 @@ Command Line Options
| `-copybuffersize ` | Size of the
[
https://issues.apache.org/jira/browse/HADOOP-17531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HADOOP-17531:
Labels: pull-request-available (was: )
> DistCp: Reduce memory usage on copying huge
[
https://issues.apache.org/jira/browse/HADOOP-17531?focusedWorklogId=559838=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559838
]
ASF GitHub Bot logged work on HADOOP-17531:
---
Author: ASF GitHub Bot
ayushtkn opened a new pull request #2732:
URL: https://github.com/apache/hadoop/pull/2732
https://issues.apache.org/jira/browse/HADOOP-17531
This is an automated message from the Apache Git Service.
To respond to the
[
https://issues.apache.org/jira/browse/HADOOP-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumangala Patki updated HADOOP-17548:
-
Description: The call to mkdirs with overwrite set to true results in an
additional
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559823=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559823
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788654337
@iwasakims I've updated the description of `ipc.client.rpc-timeout.ms` in
hadoop/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
You can
bibinchundatt commented on pull request #2719:
URL: https://github.com/apache/hadoop/pull/2719#issuecomment-788629039
@Neilxzn will take a look by this weekend
This is an automated message from the Apache Git Service.
To
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559808=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559808
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788624136
> @functioner Just update the value of
`CommonConfigurationKeys.IPC_CLIENT_RPC_TIMEOUT_DEFAULT` and core-default.xml
if you want to change the default timeout.
Hexiaoqiao commented on pull request #2721:
URL: https://github.com/apache/hadoop/pull/2721#issuecomment-788595297
Committed to trunk. Thanks @qizhu-lucas for your contributions. Thanks
@ayushtkn and @jojochuang for your reviews.
Hexiaoqiao merged pull request #2721:
URL: https://github.com/apache/hadoop/pull/2721
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559758=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559758
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
iwasakims commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788576411
@functioner Just update the value of
`CommonConfigurationKeys.IPC_CLIENT_RPC_TIMEOUT_DEFAULT` and core-default.xml
if you want to change the default timeout.
Neilxzn commented on pull request #2719:
URL: https://github.com/apache/hadoop/pull/2719#issuecomment-788551894
@bibinchundatt Can you please take a look at this PR? thx
This is an automated message from the Apache Git
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559722=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559722
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner removed a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788507261
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559721=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559721
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner removed a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788419641
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559712=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559712
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559713=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559713
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559711=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559711
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559710=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559710
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
qizhu-lucas commented on pull request #2721:
URL: https://github.com/apache/hadoop/pull/2721#issuecomment-788521571
@jojochuang
Could you help check the latest patch?
Thanks.
This is an automated message from the
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559703=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559703
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559702=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559702
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559701=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559701
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559700=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559700
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559699=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559699
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
functioner commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788518502
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))", and it
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559695=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559695
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788507261
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))",
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559693=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559693
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788507261
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))", and it
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559659=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559659
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788419641
> > According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))", and it
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559649=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559649
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
iwasakims commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788413458
> According to the comment in that test case, it "should not time out
because effective rpc-timeout is multiple of ping interval: 1600 (= 800 * (1000
/ 800 + 1))", and it
Ahmed Hussein created HADOOP-17557:
--
Summary: skip-dirs option is not processed by Yetus
Key: HADOOP-17557
URL: https://issues.apache.org/jira/browse/HADOOP-17557
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559447=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559447
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788083854
> > @functioner see TestRPC#testClientRpcTimeout
> > Maybe It is expected that Send ping all the time when
_ipc.client.rpc-timeout.ms_ less than 0.
> > @iwasakims Do you
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559439=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559439
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
functioner commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-788070811
> From the description of
[HADOOP-17552](https://issues.apache.org/jira/browse/HADOOP-17552):
>
> > We are doing some systematic fault injection testing in Hadoop-3.2.2
tomscut commented on pull request #2668:
URL: https://github.com/apache/hadoop/pull/2668#issuecomment-788061149
Hi @arp7 , could you take a quick look at this? Let's see if there are any
other questions. Thank you.
This is
tomscut commented on pull request #2718:
URL: https://github.com/apache/hadoop/pull/2718#issuecomment-788058754
> Okay I see, the only failure is the two unrelated unit tests. I will merge
this shortly.
Thank you very much.
arp7 merged pull request #2718:
URL: https://github.com/apache/hadoop/pull/2718
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
arp7 commented on pull request #2718:
URL: https://github.com/apache/hadoop/pull/2718#issuecomment-788056433
Okay I see, the only failure is the two unrelated unit tests. I will merge
this shortly.
This is an automated
tomscut edited a comment on pull request #2718:
URL: https://github.com/apache/hadoop/pull/2718#issuecomment-788048147
> Hi @tomscut, I don't see where the Jenkins checks have run successfully.
Can you point me to the report?
Hi @arp7 , thanks for your review.
I saw
tomscut commented on pull request #2718:
URL: https://github.com/apache/hadoop/pull/2718#issuecomment-788048147
> Hi @tomscut, I don't see where the Jenkins checks have run successfully.
Can you point me to the report?
Hi @arp7 , thanks for your review.
I saw pre-check
arp7 commented on pull request #2718:
URL: https://github.com/apache/hadoop/pull/2718#issuecomment-788042878
Hi @tomscut, I don't see where the Jenkins checks have run successfully. Can
you point me to the report?
This is
qizhu-lucas commented on pull request #2721:
URL: https://github.com/apache/hadoop/pull/2721#issuecomment-788040129
I think the test failed is not related to this.
This is an automated message from the Apache Git
mukul1987 commented on pull request #2728:
URL: https://github.com/apache/hadoop/pull/2728#issuecomment-788011190
@karthikhw , the patch generally looks good to me, However what are the
cases when the nodes is null ?
This
mukul1987 closed pull request #2728:
URL: https://github.com/apache/hadoop/pull/2728
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
[
https://issues.apache.org/jira/browse/HADOOP-17532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292920#comment-17292920
]
Bhavik Patel commented on HADOOP-17532:
---
is the issue here caused by the conflicting version from
[
https://issues.apache.org/jira/browse/HADOOP-17471?focusedWorklogId=559400=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559400
]
ASF GitHub Bot logged work on HADOOP-17471:
---
Author: ASF GitHub Bot
mehakmeet commented on pull request #2731:
URL: https://github.com/apache/hadoop/pull/2731#issuecomment-787996700
Need to remove DurationTrackers from streams, since now I am collecting them
from AbfsRestOperation.
This is
[
https://issues.apache.org/jira/browse/HADOOP-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292910#comment-17292910
]
Mehakmeet Singh commented on HADOOP-17553:
--
So, few doubts I had:
* Creating JSON is also
[
https://issues.apache.org/jira/browse/HADOOP-17471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HADOOP-17471:
Labels: pull-request-available (was: )
> ABFS to collect IOStatistics
>
[
https://issues.apache.org/jira/browse/HADOOP-17471?focusedWorklogId=559393=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559393
]
ASF GitHub Bot logged work on HADOOP-17471:
---
Author: ASF GitHub Bot
mehakmeet opened a new pull request #2731:
URL: https://github.com/apache/hadoop/pull/2731
Tested by: mvn -T 16 -Dparallel-tests=abfs clean verify
Region: East US
```
[INFO] Results:
[INFO]
[INFO] Tests run: 95, Failures: 0, Errors: 0, Skipped: 0
```
```
Adam Roberts created HADOOP-17556:
-
Summary: Understanding Netty versions and upgrading them (three
findings in Hadoop we could upgrade?)
Key: HADOOP-17556
URL: https://issues.apache.org/jira/browse/HADOOP-17556
Adam Roberts created HADOOP-17555:
-
Summary: Image scan shows something in Hadoop using
jackson-databind 2.4.0...what?
Key: HADOOP-17555
URL: https://issues.apache.org/jira/browse/HADOOP-17555
JJiaguodong opened a new pull request #2730:
URL: https://github.com/apache/hadoop/pull/2730
Fix some spelling errors
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
Zhangshunyu commented on pull request #2655:
URL: https://github.com/apache/hadoop/pull/2655#issuecomment-787926710
@PHILO-HE by the way, the read write lock in
org/apache/hadoop/hdfs/server/datanode/BlockSender.java:267
`try(AutoCloseableLock lock =
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559323=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559323
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559324=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559324
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
iwasakims edited a comment on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-787853012
@functioner @ferhui, I made the timeout configurable by introducing
`ipc.client.rpc-timeout.ms` in
[HADOOP-11252](https://issues.apache.org/jira/browse/HADOOP-11252).
iwasakims commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-787876863
From the description of
[HADOOP-17552](https://issues.apache.org/jira/browse/HADOOP-17552):
> We are doing some systematic fault injection testing in Hadoop-3.2.2 and
[
https://issues.apache.org/jira/browse/HADOOP-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masatake Iwasaki reassigned HADOOP-17552:
-
Assignee: (was: Masatake Iwasaki)
> The read method of
[
https://issues.apache.org/jira/browse/HADOOP-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masatake Iwasaki reassigned HADOOP-17552:
-
Assignee: Masatake Iwasaki
> The read method of
[
https://issues.apache.org/jira/browse/HADOOP-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masatake Iwasaki updated HADOOP-17552:
--
Priority: Major (was: Critical)
> The read method of
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559305=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559305
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
iwasakims commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-787854585
I think the long default timeout (kicked by tcp_retries2) surfaced as RM-HA
(YARN) issue like [YARN-2578](https://issues.apache.org/jira/browse/YARN-2587)
rather than HDFS
[
https://issues.apache.org/jira/browse/HADOOP-17552?focusedWorklogId=559303=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-559303
]
ASF GitHub Bot logged work on HADOOP-17552:
---
Author: ASF GitHub Bot
iwasakims commented on pull request #2727:
URL: https://github.com/apache/hadoop/pull/2727#issuecomment-787853012
@functioner @ferhui, I made the timeout configurable by introducing
`ipc.client.rpc-timeout.ms` in
[HADOOP-11252](https://issues.apache.org/jira/browse/HADOOP-11252). Since
[
https://issues.apache.org/jira/browse/HADOOP-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumangala Patki updated HADOOP-17548:
-
Summary: ABFS: Config for Mkdir overwrite (was: ABFS: Change mkdirs
default overwrite
sumangala-patki opened a new pull request #2729:
URL: https://github.com/apache/hadoop/pull/2729
The call to mkdirs with overwrite set to true results in an overhead set
property call (LMT update, etc), which is unnecessary. Moreover, mkdirs on an
existing file path returns success. This
[
https://issues.apache.org/jira/browse/HADOOP-17548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumangala Patki updated HADOOP-17548:
-
Description: The call to mkdirs with overwrite set to true results in an
overhead set
karthikhw opened a new pull request #2728:
URL: https://github.com/apache/hadoop/pull/2728
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
91 matches
Mail list logo
