[
https://issues.apache.org/jira/browse/HUDI-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964154#comment-16964154
]
Vinoth Chandar commented on HUDI-312:
-------------------------------------
> Embedded timeline had been enabled for some time now. So, it is still not
> clear if embedded timeline server is causing it.
Given its a feature we recommend to users, I would suggest not to disable this
right away.
@uditme This is where we are now.
Next steps could be :
* Dump out the logs (currently logs are printed after command succeeds) as the
command makes progress and see where the hang is at
* Try force killing the jvm after that point and see if it exits atleast. (I
tried added System.exit(0) to last line of DeltaStreamer::main and it did not
do the trick.
> Investigate recent flaky CI runs
> --------------------------------
>
> Key: HUDI-312
> URL: https://issues.apache.org/jira/browse/HUDI-312
> Project: Apache Hudi (incubating)
> Issue Type: New Feature
> Components: Testing
> Reporter: Vinoth Chandar
> Assignee: leesf
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.1
>
> Attachments: Builds - apache_incubator-hudi - Travis CI.pdf
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> master used to be solid green. noticing that nowadays PRs and even some
> master merges fail with
> - No output received for 10m
> - Exceeded runtime of 50m
> - VM exit crash
> We saw this earlier in the year as well. It was due to the apache org queue
> in travis being busy/stressed. I think we should shadow azure CI or circle CI
> parallely and weed out code vs environment issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
