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

Ivan A. Veselovsky updated PIG-2898:
------------------------------------

    Attachment: PIG-2898-trunk-5.patch

Hi, Rohini,
all the mentioned suggestions were adderessed in the patch #5. This patch is 
cumulative: it aggregates all the changes made in previous patches.

Notes:

* In parallellized mode context (like "[myfile.conf-MyGroup]" is printed 
*after* the results due to formatting issues (some contexts are too long).

* In trunk branch test streaming_local.conf/StreamingLocal_11 hangs in local 
mode (observed in both sequential and parallel execution modes). So, I 
recommend to comment it out to get full results. 

* The local dir parametrized with 'hadoop.mapred.local.dir' in ant, or 
'HADOOP_MAPRED_LOCAL_DIR' in environment.

* Debug output parametrized with 'e2e.debug' in ant, or 'E2E_DEBUG' in 
environment. 
                
> Parallel execution of e2e tests
> -------------------------------
>
>                 Key: PIG-2898
>                 URL: https://issues.apache.org/jira/browse/PIG-2898
>             Project: Pig
>          Issue Type: Improvement
>          Components: e2e harness
>    Affects Versions: 0.10.0
>            Reporter: Andrey Klochkov
>            Assignee: Ivan A. Veselovsky
>              Labels: test
>         Attachments: PIG-2898-against-trunk-2.patch, 
> PIG-2898-fix-sub-prototypes.patch, PIG-2898-trunk-3.patch, 
> PIG-2898-trunk-5.patch
>
>
> Today it takes ~19 hours to run the full set of e2e tests in mapred mode. The 
> bottleneck here is the client side, and per our observations it can help a 
> lot if the e2e harness would be able to run tests in parallel threads.
> We prototyped changes in e2e harness allowing to run tests in a configurable 
> number of threads. Preliminary results show more than 6x reduction in 
> execution time when using a small 3-nodes M/R cluster with modest 
> configuration. Going to share a patch shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to