date:20151109

[jira] [Commented] (KAFKA-2779) Kafka SSL transport layer leaks file descriptors

2015-11-09 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/KAFKA-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996495#comment-14996495
 ] 

ASF GitHub Bot commented on KAFKA-2779:
---

GitHub user rajinisivaram opened a pull request:

https://github.com/apache/kafka/pull/460

KAFKA-2779: Close SSL socket channel on remote connection close

Close socket channel in finally block to avoid file descriptor leak when 
remote end closes the connection

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rajinisivaram/kafka KAFKA-2779

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/460.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #460


commit c1ddae064d38f2cda09c1aa0475c142a0937f3f3
Author: Rajini Sivaram 
Date:   2015-11-09T13:04:03Z

KAFKA-2779: Close SSL socket channel on remote connection close to avoid 
file descriptor leak




> Kafka SSL transport layer leaks file descriptors
> 
>
> Key: KAFKA-2779
> URL: https://issues.apache.org/jira/browse/KAFKA-2779
> Project: Kafka
>  Issue Type: Bug
>  Components: network
>Affects Versions: 0.9.0.0
>Reporter: Rajini Sivaram
>Assignee: Rajini Sivaram
>Priority: Critical
>
> There is currently no transition from read() to close() in SslTransportLayer 
> to handle graceful shutdown requests. As a result, Kafka SSL connections are 
> never shutdown gracefully. In addition to this, close() does not handle 
> ungraceful termination of connections correctly. If flush() fails because the 
> other end has performed a close (eg. because graceful termination was not 
> handled), Kafka prints out a warning and does not close the socket. This 
> leaks file descriptors.
> We are seeing a large number of open file descriptors because our health 
> checks to Kafka result in connections that are neither terminated gracefully 
> nor closed correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] kafka pull request: KAFKA-2779: Close SSL socket channel on remote...

2015-11-09 Thread rajinisivaram

GitHub user rajinisivaram opened a pull request:

https://github.com/apache/kafka/pull/460

KAFKA-2779: Close SSL socket channel on remote connection close

Close socket channel in finally block to avoid file descriptor leak when 
remote end closes the connection

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rajinisivaram/kafka KAFKA-2779

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/460.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #460


commit c1ddae064d38f2cda09c1aa0475c142a0937f3f3
Author: Rajini Sivaram 
Date:   2015-11-09T13:04:03Z

KAFKA-2779: Close SSL socket channel on remote connection close to avoid 
file descriptor leak




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: kafka_system_tests #142

2015-11-09 Thread ewen

See 

--
Started by user benstopford
Building on master in workspace 

[kafka_system_tests] $ /bin/bash /tmp/hudson8577356696053981129.sh
Running command: which virtualenv

Running command: . venv/bin/activate; cd 
 `which pip` 
uninstall -y kafkatest; `which pip` uninstall -y ducktape
Uninstalling kafkatest-0.9.0.0.dev0:
Successfully uninstalled kafkatest-0.9.0.0.dev0
Uninstalling ducktape-0.3.8:
Successfully uninstalled ducktape-0.3.8

Running command: . venv/bin/activate; cd 
 `which 
python` setup.py develop

Running command: cd 
 git pull && 
./gradlew clean jar
error: Your local changes to the following files would be overwritten by merge:
tests/kafkatest/tests/copycat_distributed_test.py
tests/kafkatest/tests/copycat_rest_test.py
tests/kafkatest/tests/copycat_test.py
Please, commit your changes or stash them before you can merge.
Aborting
Updating b4e1bdf..f2031d4

Command failed: cd 
 git pull && 
./gradlew clean jar
Running command: cd 
 vagrant destroy 
-f

Build step 'Execute shell' marked build as failure

[jira] [Updated] (KAFKA-2779) Kafka SSL transport layer leaks file descriptors

2015-11-09 Thread Rajini Sivaram (JIRA)


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

Rajini Sivaram updated KAFKA-2779:
--
Status: Patch Available  (was: Open)

Move socket close to finally block to avoid leaking file descriptors when 
graceful close message cannot be sent because remote end has already closed the 
connection.

> Kafka SSL transport layer leaks file descriptors
> 
>
> Key: KAFKA-2779
> URL: https://issues.apache.org/jira/browse/KAFKA-2779
> Project: Kafka
>  Issue Type: Bug
>  Components: network
>Affects Versions: 0.9.0.0
>Reporter: Rajini Sivaram
>Assignee: Rajini Sivaram
>Priority: Critical
>
> There is currently no transition from read() to close() in SslTransportLayer 
> to handle graceful shutdown requests. As a result, Kafka SSL connections are 
> never shutdown gracefully. In addition to this, close() does not handle 
> ungraceful termination of connections correctly. If flush() fails because the 
> other end has performed a close (eg. because graceful termination was not 
> handled), Kafka prints out a warning and does not close the socket. This 
> leaks file descriptors.
> We are seeing a large number of open file descriptors because our health 
> checks to Kafka result in connections that are neither terminated gracefully 
> nor closed correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Vector file of logo

2015-11-09 Thread Peter LaPierre

Hello there,

Does anyone have a Vector file of the Apache Kafka logo that we can use?

Kind regards
~Peter

[GitHub] kafka pull request: MINOR: remove old producer in config sections ...

2015-11-09 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/468


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] kafka pull request: MINOR: Make sure generated docs don't get chec...

2015-11-09 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/469


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (KAFKA-2784) Mirror maker should swallow exceptions during shutdown.

2015-11-09 Thread Jiangjie Qin (JIRA)

Jiangjie Qin created KAFKA-2784:
---

 Summary: Mirror maker should swallow exceptions during shutdown.
 Key: KAFKA-2784
 URL: https://issues.apache.org/jira/browse/KAFKA-2784
 Project: Kafka
  Issue Type: Bug
Reporter: Jiangjie Qin
Assignee: Jiangjie Qin


Mirror maker should swallow exceptions during shutdown to make sure shutdown 
latch is pulled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: kafka-trunk-jdk8 #120

2015-11-09 Thread Apache Jenkins Server

See 

Changes:

[cshapi] MINOR: remove old producer in config sections to align with APIs

[wangguoz] MINOR: Improve exception message that gets thrown for non-existent 
group

[wangguoz] MINOR: Make sure generated docs don't get checked in

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/kafka.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/kafka.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/kafka.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/trunk^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/trunk^{commit} # timeout=10
Checking out Revision e2794a79c8d2e8ae9cf30bfe10bbed34951a004b 
(refs/remotes/origin/trunk)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e2794a79c8d2e8ae9cf30bfe10bbed34951a004b
 > git rev-list 359be3a682951fd469d690df8d9e7a5a89a9d03b # timeout=10
Setting 
GRADLE_2_1_HOME=/home/jenkins/jenkins-slave/tools/hudson.plugins.gradle.GradleInstallation/Gradle_2.1
Setting 
JDK1_8_0_45_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk1.8.0_45
[kafka-trunk-jdk8] $ /bin/bash -xe /tmp/hudson2277902522427229263.sh
+ 
/home/jenkins/jenkins-slave/tools/hudson.plugins.gradle.GradleInstallation/Gradle_2.1/bin/gradle
To honour the JVM settings for this build a new JVM will be forked. Please 
consider using the daemon: 
http://gradle.org/docs/2.1/userguide/gradle_daemon.html.
Building project 'core' with Scala version 2.10.5
:downloadWrapper UP-TO-DATE

BUILD SUCCESSFUL

Total time: 15.803 secs
Setting 
GRADLE_2_1_HOME=/home/jenkins/jenkins-slave/tools/hudson.plugins.gradle.GradleInstallation/Gradle_2.1
Setting 
JDK1_8_0_45_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk1.8.0_45
[kafka-trunk-jdk8] $ /bin/bash -xe /tmp/hudson284449076317262977.sh
+ ./gradlew -Dorg.gradle.project.maxParallelForks=1 clean jarAll docsJarAll 
testAll
To honour the JVM settings for this build a new JVM will be forked. Please 
consider using the daemon: 
https://docs.gradle.org/2.8/userguide/gradle_daemon.html.
Building project 'core' with Scala version 2.10.5
:clean UP-TO-DATE
:clients:clean
:connect:clean UP-TO-DATE
:core:clean
:examples:clean UP-TO-DATE
:log4j-appender:clean UP-TO-DATE
:streams:clean UP-TO-DATE
:tools:clean UP-TO-DATE
:connect:api:clean UP-TO-DATE
:connect:file:clean UP-TO-DATE
:connect:json:clean UP-TO-DATE
:connect:runtime:clean UP-TO-DATE
:jar_core_2_10_5
Building project 'core' with Scala version 2.10.5
:kafka-trunk-jdk8:clients:compileJava
:jar_core_2_10_5 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Failed to capture snapshot of input files for task 'compileJava' during 
up-to-date check.  See stacktrace for details.
> Could not add entry 
> '
>  to cache fileHashes.bin 
> (

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output.

BUILD FAILED

Total time: 15.067 secs
Build step 'Execute shell' marked build as failure
Recording test results
Setting 
GRADLE_2_1_HOME=/home/jenkins/jenkins-slave/tools/hudson.plugins.gradle.GradleInstallation/Gradle_2.1
Setting 
JDK1_8_0_45_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk1.8.0_45
ERROR: Publisher 'Publish JUnit test result report' failed: No test report 
files were found. Configuration error?
Setting 
GRADLE_2_1_HOME=/home/jenkins/jenkins-slave/tools/hudson.plugins.gradle.GradleInstallation/Gradle_2.1
Setting 
JDK1_8_0_45_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk1.8.0_45

[jira] [Created] (KAFKA-2790) Kafka 0.9.0 doc improvement

2015-11-09 Thread Jun Rao (JIRA)

Jun Rao created KAFKA-2790:
--

Summary: Kafka 0.9.0 doc improvement
Key: KAFKA-2790
URL: https://issues.apache.org/jira/browse/KAFKA-2790
Project: Kafka
Issue Type: Improvement
Affects Versions: 0.9.0.0
Reporter: Jun Rao
Fix For: 0.9.0.0

Observed a few issues after uploading the 0.9.0 docs to the Apache site
(http://kafka.apache.org/090/documentation.html).

1. There are a few places still mentioning 0.8.2.

docs/api.html:We are in the process of rewritting the JVM clients for Kafka. As
of 0.8.2 Kafka includes a newly rewritten Java producer. The next release will
include an equivalent Java consumer. These new clients are meant to supplant
the existing Scala clients, but for compatability they will co-exist for some
time. These clients are available in a seperate jar with minimal dependencies,
while the old Scala clients remain packaged with the server.

docs/api.html:As of the 0.8.2 release we encourage all new development to use
the new Java producer. This client is production tested and generally both
faster and more fully featured than the previous Scala client. You can use this
client by adding a dependency on the client jar using the following example
maven co-ordinates (you can change the version numbers with new releases):

docs/api.html: version0.8.2.0/version

docs/ops.html:The partition reassignment tool does not have the ability to
automatically generate a reassignment plan for decommissioning brokers yet. As
such, the admin has to come up with a reassignment plan to move the replica for
all partitions hosted on the broker to be decommissioned, to the rest of the
brokers. This can be relatively tedious as the reassignment needs to ensure
that all the replicas are not moved from the decommissioned broker to only one
other broker. To make this process effortless, we plan to add tooling support
for decommissioning brokers in 0.8.2.

docs/quickstart.html:https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.0/kafka_2.10-0.8.2.0.tgz;
title="Kafka downloads">Download the 0.8.2.0 release and un-tar it.
docs/quickstart.html: tar -xzf kafka_2.10-0.8.2.0.tgz
docs/quickstart.html: cd kafka_2.10-0.8.2.0

1 2 >

1 - 100 of 164 matches

Mail list logo