It is moving average of last minute.
On Sun, Feb 25, 2018 at 12:42 AM, Soheil Pourbafrani
wrote:
> Thanks, Manikumar, You mean one minute's average from start time or for
> last minute?
>
> On Sat, Feb 24, 2018 at 7:06 PM, Manikumar
> wrote:
>
Hello!
This is a very general question but I was wondering if anyone knows whether
or not the Kafka brokers need to do any additional work to receive/respond
to requests coming in from older clients.
Even though newer brokers support older clients, is there any additional
processing time that
Thanks, Manikumar, You mean one minute's average from start time or for
last minute?
On Sat, Feb 24, 2018 at 7:06 PM, Manikumar
wrote:
> They are 1-, 5-, and 15-minute moving averages.
> Kafka brokers uses dropwizard/yammer metric library.
> More details about metrics
Please take a look at maxSessionTimeout under:
http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_advancedConfiguration
On Sat, Feb 24, 2018 at 9:46 AM, Soheil Pourbafrani
wrote:
> Thanks, Manna, Can you say which property (in Kafka or Zookeeper) should I
>
Thanks, Manna, Can you say which property (in Kafka or Zookeeper) should I
increase?
On Sat, Feb 24, 2018 at 7:49 PM, M. Manna wrote:
> Have you tried increasing the timeouts for zookeeper nodes and Kafka
> brokers to see if they make a difference?
>
>
>
> On Sat, 24 Feb
Hello,
I have found this description in only documentation (without taking into
account spelling errors 'byes of messages'), a question stays in my mind ...
what happens if the size does not fall correctly on a message number?
Example if in one parition I have 10(messages) of 1024 bytes --> I
Have you tried increasing the timeouts for zookeeper nodes and Kafka
brokers to see if they make a difference?
On Sat, 24 Feb 2018 at 14:55, Soheil Pourbafrani
wrote:
> Hi and Thanks,
> Excuse me, The Kafka version is 0.11 and Zookeeper version is 3.4.10
>
> I've check
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 1.1.0.
This is minor version release of Apache Kakfa. It Includes 29 new KIPs.
Please see the release plan for more details:
They are 1-, 5-, and 15-minute moving averages.
Kafka brokers uses dropwizard/yammer metric library.
More details about metrics are here :
http://metrics.dropwizard.io/2.2.0/getting-started/
On Sat, Feb 24, 2018 at 8:31 PM, Soheil Pourbafrani
wrote:
> Hi,
>
> What is the
Hi,
What is the exact meaning of the Kafka metrics attributes, for example, the
attribute
kafka.server:type=BrokerTopicMetrics,name=BytesInPerSec
has the attributes MeanRate and OneMinuteRate. I am confused about the
attribute OneMinuteRate! It is for the last minutes or for the whole broker
Hi and Thanks,
Excuse me, The Kafka version is 0.11 and Zookeeper version is 3.4.10
I've check Zookeeper logs and sessions are expiring and renewing
continuously there. I use the same Zookeeper cluster for Hadoop HA and it
works well.
I Answer the same question with more details in the following
Have you seen this thread (GC might be the cause for session time out) ?
http://search-hadoop.com/m/Kafka/uyzND15d4h21yZnIZ?subj=Re+zookeeper+session+time+out
Please check zookeeper server logs when you have a chance.
Please share the versions of Kafka and zookeeper.
On Sat, Feb 24, 2018 at
set level of
log4j.logger.org.I0Itec.zkclient.ZkClient=INFO
log4j.logger.org.apache.zookeeper=INFO
from INFO to WARN
in log4j.properties
On 01/24/2018 17:11,José Ribeiro wrote:
I didn't touch the properties of any configuration. I even tried to download
again the
In Kafka 0.11 server.log, it continuously logs
[2018-02-24 10:38:11,178] WARN Client session timed out, have not heard
from server in 4001ms for sessionid 0x361c65434f1000c
(org.apache.zookeeper.ClientCnxn)
[2018-02-24 10:38:11,178] INFO Client session timed out, have not heard
from server in
14 matches
Mail list logo