Hi all, I'd like to submit https://issues.apache.org/jira/browse/KAFKA-9258 for blocker consideration. This issue affects the Connect framework and causes a 500 error to be thrown from the REST API when restarting a task that has failed during startup, even after the connector has been reconfigured. This is a regression and does not occur in any versions of Connect prior to 2.4 release candidates. There is a PR already opened for this issue that I've tested and verified so we should be able to merge quickly if this is approved as a blocker.
Cheers, Chris On Mon, Dec 2, 2019 at 1:31 PM Eric Lalonde <e...@autonomic.ai> wrote: > Hi all, > > I ran the following: > > $ git clone https://github.com/elalonde/kafka < > https://github.com/elalonde/kafka> > $ ./kafka/bin/verifykafka-rc.sh 2.4.0 > https://home.apache.org/~manikumar/kafka-2.4.0-rc2 < > https://home.apache.org/~manikumar/kafka-2.4.0-rc2> > > - All sha1, sha256 and md5 sums look good > - pgp signatures look good > - unit tests pass > - Integration tests pass with the following issue: > > <=------------> 12% EXECUTING [30m 21s] > <=------------> 12% EXECUTING [30m 22s]mpleted, 16 skipped > > IDLE > <=------------> 12% EXECUTING [30m 27s] > > IDLE > > IDLE > > IDLE > > :core:integrationTest > Executing test > kafka.api.AuthorizerIntegrationTest > > IDLE > > IDLE > > > After 30 minutes the above test had not finished, seemed stalled, so I > cancelled it. LMK if I am overly impatient. > >
