[jira] [Created] (BIGTOP-3152) No need to Force the use of Netty over Hadoop RPC in Giraph

2019-01-30 Thread Yuqi Gu (JIRA)
Yuqi Gu created BIGTOP-3152:
---

 Summary: No need to Force the use of Netty over Hadoop RPC in 
Giraph
 Key: BIGTOP-3152
 URL: https://issues.apache.org/jira/browse/BIGTOP-3152
 Project: Bigtop
  Issue Type: Improvement
  Components: deployment
Reporter: Yuqi Gu
Assignee: Yuqi Gu
 Fix For: 1.4.0


For workaround for GIRAPH-198 originally, giraph activated netty rpc by setting 
giraph.useNetty from command line.
In GIRAPH-200 later, giraph removed hadoop RPC and keep just netty by default.
So we can remove the Netty  configuration accordingly.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (BIGTOP-3151) Add flink smoke test

2019-01-30 Thread Jun He (JIRA)
Jun He created BIGTOP-3151:
--

 Summary: Add flink smoke test
 Key: BIGTOP-3151
 URL: https://issues.apache.org/jira/browse/BIGTOP-3151
 Project: Bigtop
  Issue Type: Bug
Reporter: Jun He
Assignee: Jun He


Add flink to smoke tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Let's Encrypt certificate expiration notice for domain "ci.bigtop.apache.org"

2019-01-30 Thread Evans Ye
The cert has been renewed.

Evans Ye  於 2018年8月2日 週四 上午12:01寫道:

> The cert expire on 8/1. I've it renewed.
>
> Konstantin Boudnik  於 2017年6月15日 週四 上午9:43寫道:
>
>> Thanks Olaf, that's great! I wonder if we simply can add a job to be
>> ran on master whenever we need it or, perhaps proactive, every X
>> months?
>> --
>>   Take care,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Wed, Jun 14, 2017 at 11:36 AM, Olaf Flebbe  wrote:
>> > Hi Cos.
>> >
>> > Yes of course there is.: The setup guide of the CI.
>> >
>> >
>> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide
>> >
>> > The very last paragraph "Renewing the cert" contains three commandlines
>> to
>> > be executed in order on "master".
>> >
>> > Ah and BTW, I did run these three commands in consecutive order right
>> now
>> > ;-)
>> >
>> > Olaf
>> >
>> >
>> >
>> > Am 14.06.2017 um 19:31 schrieb Konstantin Boudnik :
>> >
>> > Thanks man! Are there a wiki of some kind (or maybe an email) on how
>> > to do this? It seems like you're pushing this all along. Just let us
>> > know if you need some help!
>> >
>> > Cos
>> > --
>> >  Take care,
>> > Konstantin (Cos) Boudnik
>> >
>> >
>> > On Wed, Jun 14, 2017 at 10:03 AM, Olaf Flebbe  wrote:
>> >
>> > Will fix this later today
>> >
>> > Am 14.06.2017 um 12:02 schrieb Let's Encrypt Expiry Bot
>> > :
>> >
>> > Hello,
>> >
>> > Your certificate (or certificates) for the names listed below will
>> expire in
>> > 9 days (on 24 Jun 17 09:41 +). Please make sure to renew
>> > your certificate before then, or visitors to your website will encounter
>> > errors.
>> >
>> > ci.bigtop.apache.org
>> >
>> > For any questions or support, please visit
>> > https://community.letsencrypt.org/.
>> > Unfortunately, we can't provide support by email.
>> >
>> > For details about when we send these emails, please visit
>> > https://letsencrypt.org/docs/expiration-emails/. In particular, note
>> > that this reminder email is still sent if you've obtained a slightly
>> > different certificate by adding or removing names. If you've replaced
>> > this certificate with a newer one that covers more or fewer names than
>> > the list above, you may be able to ignore this message.
>> >
>> > If you want to stop receiving all email from this address, click
>> >
>> http://mandrillapp.com/track/unsub.php?u=30850198=4a7180e49d934d5f937f8e924574e3cf.iYH%2BI%2FaRl5%2F6euy86DZLxmewGyM%3D=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Ddev%2540bigtop.apache.org
>> > (Warning: this is a one-click action that cannot be undone)
>> >
>> > Regards,
>> > The Let's Encrypt Team
>> >
>> >
>>
>


[jira] [Created] (BIGTOP-3150) [Provisioner] Raise proper exit code and error messages when provisioning failed

2019-01-30 Thread Evans Ye (JIRA)
Evans Ye created BIGTOP-3150:


 Summary: [Provisioner] Raise proper exit code and error messages 
when provisioning failed
 Key: BIGTOP-3150
 URL: https://issues.apache.org/jira/browse/BIGTOP-3150
 Project: Bigtop
  Issue Type: Sub-task
  Components: provisioner
Affects Versions: 1.3.0
Reporter: Evans Ye
Assignee: Evans Ye


When running ./gradlew docker-provisioner, the result will always be BUILD 
SUCCESSFUL, even if the provisioning failed. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)