Build failed in Jenkins: pulsar-master #712

[Apache Jenkins Server]

See 


Changes:

[github] Set correct exception if function runnable fails with Error (#2353)

--
[...truncated 1.00 MB...]
[INFO] Pulsar Functions :: API Examples ... SUCCESS [  5.235 s]
[INFO] Pulsar Functions :: Runtime Shaded . SUCCESS [ 15.192 s]
[INFO] Pulsar Functions :: Runtime All  SUCCESS [ 32.119 s]
[INFO] Pulsar IO :: Aerospike . SUCCESS [  5.679 s]
[INFO] Pulsar IO :: Kafka . SUCCESS [  5.692 s]
[INFO] Pulsar IO :: RabbitMQ .. SUCCESS [  5.449 s]
[INFO] Pulsar IO :: Kinesis ... SUCCESS [ 14.086 s]
[INFO] Pulsar :: Distribution . SUCCESS [  2.137 s]
[INFO] Pulsar :: Distribution :: Server ... SUCCESS [ 21.395 s]
[INFO] Pulsar :: Distribution :: IO ... SUCCESS [  5.855 s]
[INFO] Apache Pulsar :: Docker Images . SUCCESS [  2.130 s]
[INFO] Apache Pulsar :: Docker Images :: Pulsar Latest Version SUCCESS [  5.542 
s]
[INFO] Apache Pulsar :: Docker Images :: Grafana .. SUCCESS [  2.170 s]
[INFO] Apache Pulsar :: Docker Images :: Pulsar Latest Version (Include All 
Components) SUCCESS [  2.433 s]
[INFO] Apache Pulsar :: Tests . SUCCESS [  2.172 s]
[INFO] Apache Pulsar :: Tests :: Docker Images  SUCCESS [  2.123 s]
[INFO] Apache Pulsar :: Tests :: Docker Images :: Latest Version Testing 
SUCCESS [  2.188 s]
[INFO] Apache Pulsar :: Tests :: Integration .. SUCCESS [  9.230 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:20 h
[INFO] Finished at: 2018-08-14T06:26:24Z
[INFO] Final Memory: 225M/1799M
[INFO] 
[JENKINS] Archiving 
 to 
org.apache.pulsar/pulsar-io-kinesis/2.2.0-incubating-SNAPSHOT/pulsar-io-kinesis-2.2.0-incubating-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.pulsar/pulsar-io-kinesis/2.2.0-incubating-SNAPSHOT/pulsar-io-kinesis-2.2.0-incubating-SNAPSHOT.jar
[Fast Archiver] Compressed 29.45 MB of artifacts by 96.4% relative to #711
[JENKINS] Archiving 
 to 
org.apache.pulsar/pulsar-io-aerospike/2.2.0-incubating-SNAPSHOT/pulsar-io-aerospike-2.2.0-incubating-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.pulsar/pulsar-io-aerospike/2.2.0-incubating-SNAPSHOT/pulsar-io-aerospike-2.2.0-incubating-SNAPSHOT.jar
[Fast Archiver] Compressed 2.83 MB of artifacts by 87.2% relative to #711
[JENKINS] Archiving 
 to 
org.apache.pulsar/pulsar-proxy/2.2.0-incubating-SNAPSHOT/pulsar-proxy-2.2.0-incubating-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.pulsar/pulsar-proxy/2.2.0-incubating-SNAPSHOT/pulsar-proxy-2.2.0-incubating-SNAPSHOT.jar
[JENKINS] Archiving 

 to 
org.apache.pulsar/pulsar-discovery-service/2.2.0-incubating-SNAPSHOT/pulsar-discovery-service-2.2.0-incubating-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.pulsar/pulsar-discovery-service/2.2.0-incubating-SNAPSHOT/pulsar-discovery-service-2.2.0-incubating-SNAPSHOT.jar
[JENKINS] Archiving 
 to 
org.apache.pulsar/pulsar-io-kafka/2.2.0-incubating-SNAPSHOT/pulsar-io-kafka-2.2.0-incubating-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.pulsar/pulsar-io-kafka/2.2.0-incubating-SNAPSHOT/pulsar-io-kafka-2.2.0-incubating-SNAPSHOT.jar
[Fast Archiver] Compressed 4.16 MB of artifacts by 90.8% relative to #711
[JENKINS] Archiving 

 to 
org.apache.pulsar/pulsar-functions-instance/2.2.0-incubating-SNAPSHOT/pulsar-functions-instance-2.2.0-incubating-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apach

Jenkins build is still unstable: pulsar-master #711

[Apache Jenkins Server]

See 

Jenkins build is still unstable: pulsar-master #710

[Apache Jenkins Server]

See 

Re: PIP 20: Mechanism to revoke TLS authentication

[Sanjeev Kulkarni]

+1 to Sijie's suggestion to keep this inside a managed ledger.

On Mon, Aug 13, 2018 at 3:34 PM Sijie Guo  wrote:

> Ivan,
>
> Thank you for writing this up. This PIP looks great to me! +1
>
> just one question:
>
> > This will add the subject key identifier to zookeeper under
> /tls/revoked/. All brokers and proxies cache the children
> /tls/revoked.
>
> Instead of using zookeeper, can we consider using a managed ledger or a
> system topic for keeping all these revoked keys?
>
> - Sijie
>
> On Tue, Aug 7, 2018 at 1:12 AM Ivan Kelly  wrote:
>
> > Hi folks,
> >
> > This is a PIP to add a mechanism to block TLS client certs from
> > accessing Pulsar if they have been compromised.
> >
> > This is a relatively small change, but I thought it best to put it to
> > the community before moving ahead with it, as people may have opinions
> > on the approach.
> >
> > The PIP is here:
> >
> >
> https://github.com/apache/incubator-pulsar/wiki/PIP-20%3A-Mechanism-to-revoke-TLS-authentication
> >
> > Cheers,
> > Ivan
> >
>

Re: PIP 20: Mechanism to revoke TLS authentication

[Sijie Guo]

Ivan,

Thank you for writing this up. This PIP looks great to me! +1

just one question:

> This will add the subject key identifier to zookeeper under
/tls/revoked/. All brokers and proxies cache the children
/tls/revoked.

Instead of using zookeeper, can we consider using a managed ledger or a
system topic for keeping all these revoked keys?

- Sijie

On Tue, Aug 7, 2018 at 1:12 AM Ivan Kelly  wrote:

> Hi folks,
>
> This is a PIP to add a mechanism to block TLS client certs from
> accessing Pulsar if they have been compromised.
>
> This is a relatively small change, but I thought it best to put it to
> the community before moving ahead with it, as people may have opinions
> on the approach.
>
> The PIP is here:
>
> https://github.com/apache/incubator-pulsar/wiki/PIP-20%3A-Mechanism-to-revoke-TLS-authentication
>
> Cheers,
> Ivan
>

Jenkins build is unstable: pulsar-master #709

[Apache Jenkins Server]

See