given full path in VM options
>>
>> *-Dlog4j.configuration=file:/Users/Chandresh/opensource/kafka/config/log4j.properties*
>>
>> still no logs in console.
>>
>> [image: Screenshot 2019-10-14 at 8.44.34 PM.png]
>>
>> On Mon, Oct 14, 2019 at 8:16 PM tao xiao wr
yes, you need to add log4j to jvm option
-Dlog4j.configuration=file:/path/to/log4j.properties
On Mon, Oct 14, 2019 at 10:33 PM chandresh pancholi <
chandreshpancholi...@gmail.com> wrote:
> Let me rephrase it.
>
> I figured out that Kafka is running successfully but i can't see logs in
> IntelliJ
TAO XIAO created KAFKA-7274:
---
Summary: Incorrect subject credential used in inter-broker
communication
Key: KAFKA-7274
URL: https://issues.apache.org/jira/browse/KAFKA-7274
Project: Kafka
Issue
+1 non-binding. thx Ismael
On Thu, 19 Apr 2018 at 23:14 Vahid S Hashemian
wrote:
> +1 (non-binding).
>
> Thanks Ismael.
>
> --Vahid
>
>
>
> From: Jorge Esteban Quilcate Otoya
> To: dev@kafka.apache.org
> Date: 04/19/2018 07:32 AM
> Subject:Re: [VOTE] Kafka 2.0.0 in June 2018
>
>
Hi Guozhang,
Are you proposing changing semantic of ack=all to acknowledge message only
after all replicas (not all ISRs, which is what Kafka currently is doing)
have committed the message? This is equivalent to setting min.isr=number of
replicas, which makes ack=all much stricter than what Kafka
+1 (non-binding)
On Fri, 19 Jan 2018 at 00:47 Rajini Sivaram wrote:
> Hi all,
>
> I would like to restart the vote for KIP-86:
>https://cwiki.apache.org/confluence/display/KAFKA/KIP-86
> %3A+Configurable+SASL+callback+handlers
>
> The KIP makes callback handlers for SASL configurable to mak
[
https://issues.apache.org/jira/browse/KAFKA-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-4129:
Status: Patch Available (was: Open)
> Processor throw exception when getting channel remote address af
TAO XIAO created KAFKA-4129:
---
Summary: Processor throw exception when getting channel remote
address after closing the channel
Key: KAFKA-4129
URL: https://issues.apache.org/jira/browse/KAFKA-4129
Project
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372982#comment-15372982
]
TAO XIAO commented on KAFKA-3950:
-
As only the topics that the users have permissio
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372705#comment-15372705
]
TAO XIAO commented on KAFKA-3950:
-
How about we still keep the filtering on client
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372705#comment-15372705
]
TAO XIAO edited comment on KAFKA-3950 at 7/12/16 11:18 AM:
---
+1
On Fri, 17 Jun 2016 at 09:03 Harsha wrote:
> +1 (binding)
> Thanks,
> Harsha
>
> On Thu, Jun 16, 2016, at 05:46 PM, Henry Cai wrote:
> > +1
> >
> > On Thu, Jun 16, 2016 at 3:46 PM, Ismael Juma wrote:
> >
> > > +1 (binding)
> > >
> > > On Fri, Jun 17, 2016 at 12:44 AM, Guozhang Wang
> > > wr
[
https://issues.apache.org/jira/browse/KAFKA-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-3787:
Status: Patch Available (was: Open)
> Preserve message timestamp in mirror mk
TAO XIAO created KAFKA-3787:
---
Summary: Preserve message timestamp in mirror mkaer
Key: KAFKA-3787
URL: https://issues.apache.org/jira/browse/KAFKA-3787
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282310#comment-15282310
]
TAO XIAO commented on KAFKA-3163:
-
[~becket_qin] Thanks. Does the KIP doc in wiki ref
[
https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282271#comment-15282271
]
TAO XIAO commented on KAFKA-3163:
-
Hi,
Do we have this KIP in the upcoming 0.10
> is shown by the topic describe command:
>
>
> Configs:segment.bytes=104857600,cleanup.policy=compact,compression.type=uncompressed
>
> On Mon, May 9, 2016 at 1:16 PM, tao xiao wrote:
>
> > You can try this
> >
> > bin/kafka-console-consumer.sh --consumer.c
You can try this
bin/kafka-console-consumer.sh --consumer.config
config/consumer.properties --from-beginning
--topic __consumer_offsets --zookeeper localhost:2181 —formatter
"kafka.coordinator.GroupMetadataManager\$OffsetsMessageFormatter"
On Mon, 9 May 2016 at 09:40 Todd Palino wrote:
> The Gr
this fix. How can I get patch for this on 0.8.2.1?
>
> Sent from my iPhone
>
> > On May 6, 2016, at 12:06 AM, tao xiao wrote:
> >
> > It said this is a duplication. This is the
> > https://issues.apache.org/jira/browse/KAFKA-2657 that KAKFA-3112
> duplicate
It said this is a duplication. This is the
https://issues.apache.org/jira/browse/KAFKA-2657 that KAKFA-3112 duplicates
to.
On Thu, 5 May 2016 at 22:13 Raj Tanneru wrote:
>
> Hi All,
> Does anyone know if KAFKA-3112 is merged to 0.9.0.1? Is there a place to
> check which version has this fix? Jir
[
https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198591#comment-15198591
]
TAO XIAO commented on KAFKA-3409:
-
This can also happen when producer is slow and bu
TAO XIAO created KAFKA-3409:
---
Summary: Mirror maker hangs indefinitely due to commit
Key: KAFKA-3409
URL: https://issues.apache.org/jira/browse/KAFKA-3409
Project: Kafka
Issue Type: Bug
TAO XIAO created KAFKA-3355:
---
Summary: GetOffsetShell command doesn't work with SASL enabled
Kafka
Key: KAFKA-3355
URL: https://issues.apache.org/jira/browse/KAFKA-3355
Project: Kafka
Issue
+1 (non-binding)
On Tue, 8 Mar 2016 at 05:33 Andrew Schofield <
andrew_schofield_j...@outlook.com> wrote:
> +1 (non-binding)
>
>
> > From: ism...@juma.me.uk
> > Date: Mon, 7 Mar 2016 19:52:11 +
> > Subject: Re: [VOTE] KIP-43: Kafka SASL enhancements
>
[
https://issues.apache.org/jira/browse/KAFKA-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133580#comment-15133580
]
TAO XIAO commented on KAFKA-3206:
-
This is most likely du
I am the author of KIP-44. I hope my use case will add some values to this
discussion. The reason I raised KIP44 is that I want to be able to
implement a custom security protocol that can fulfill the need of my
company. As pointed out by Ismael KIP-43 now supports a pluggable way to
inject custom s
Sorry, just ignore previous email. I saw the newly defined interface of the
callback in the KIP which has considered this matter.
On Fri, 29 Jan 2016 at 18:08 tao xiao wrote:
> Hi Rajini,
>
> Do you consider exposing Subject to AuthCallback as well? It is useful for
> users buildi
on from the KIP meeting on Tuesday, I have updated the KIP with a
> flow for negotiation of mechanisms to support multiple SASL mechanisms
> within a broker. I have also added a configurable Login interface to
> support custom mechanisms which require ticket refresh - requested by Tao
> X
that is a bit wired since ConsumerOffsetChecker itself does not talk to
> brokers at all, but only through ZK.
>
> Guozhang
>
> On Thu, Jan 28, 2016 at 6:07 PM, tao xiao wrote:
>
> > Guozhang,
> >
> > The old ConsumerOffsetChecker works for new consumer too with o
Guozhang,
The old ConsumerOffsetChecker works for new consumer too with offset stored
in Kafka. I tested it with mirror maker with new consumer enabled. it is
able to show offset during mirror maker running and after its shutdown.
On Fri, 29 Jan 2016 at 06:34 Guozhang Wang wrote:
> Once the off
re the JDK to add new
> security providers, I am not sure if there is value in adding more
> configuration in Kafka to add security providers.
>
> On Thu, Jan 28, 2016 at 2:25 AM, tao xiao wrote:
>
> > The callback works for me as long as it has access to Subject and mechs.
&g
[
https://issues.apache.org/jira/browse/KAFKA-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-3157:
Status: Patch Available (was: Open)
> Mirror maker doesn't commit offset with new consumer when
sswordCallback, you can define your own callbacks too if
> you require.
>
>
>
> On Wed, Jan 27, 2016 at 3:59 PM, tao xiao wrote:
>
> > Thanks Rajini. The other thing in my mind is that we should find a way to
> > expose subject to SASL so that other mechanisms are
the KIP.
>
> Regards,
>
> Rajini
>
> On Wed, Jan 27, 2016 at 2:12 AM, tao xiao wrote:
>
> > Hi Rajini,
> >
> > One requirement I have is to refresh the login token every X hours. Like
> > what the Kerberos login does I need to have a background thread that
&
[
https://issues.apache.org/jira/browse/KAFKA-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-3157:
Description:
Mirror maker doesn't commit messages with new consumer enabled when messages
are se
TAO XIAO created KAFKA-3157:
---
Summary: Mirror maker doesn't commit offset with new consumer when
there is no more messages
Key: KAFKA-3157
URL: https://issues.apache.org/jira/browse/KAFKA-3157
Pr
customize the Login code?
>
> Regards,
>
> Rajini
>
> On Tue, Jan 26, 2016 at 11:15 AM, tao xiao wrote:
>
> > Hi Rajini,
> >
> > I think it makes sense to change LoginManager or Login to an interface
> > which users can extend to provide their own logic of
Hi Rajini,
I think it makes sense to change LoginManager or Login to an interface
which users can extend to provide their own logic of login otherwise it is
hard for users to implement a custom SASL mechanism but have no control
over login
On Tue, 26 Jan 2016 at 18:45 Ismael Juma wrote:
> Hi Ra
(which are a combination of transport layer protocol
> and
>authentication protocol)?
>
>
> Regards,
>
> Rajini
>
> On Tue, Jan 26, 2016 at 6:58 AM, tao xiao wrote:
>
>
> > HI Kafka developers,
> >
> > I raised a KIP-44, allow a customized secur
HI Kafka developers,
I raised a KIP-44, allow a customized security protocol, for discussion.
The goal of this KIP to enable a customized security protocol where users
can plugin their own implementation.
Feedback is welcomed
[
https://issues.apache.org/jira/browse/KAFKA-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2993:
Component/s: producer
> compression-rate-avg always returns 0 even with compression.type being
[
https://issues.apache.org/jira/browse/KAFKA-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2993:
Status: Patch Available (was: Open)
> compression-rate-avg always returns 0 even with compression.t
[
https://issues.apache.org/jira/browse/KAFKA-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2993:
Affects Version/s: 0.9.0.0
> compression-rate-avg always returns 0 even with compression.type being
[
https://issues.apache.org/jira/browse/KAFKA-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2993:
Summary: compression-rate-avg always returns 0 even with compression.type
being set (was: compression-rate
TAO XIAO created KAFKA-2993:
---
Summary: compression-rate-avg always returns 0 event with
compression.type being set
Key: KAFKA-2993
URL: https://issues.apache.org/jira/browse/KAFKA-2993
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Description:
org.apache.kafka.clients.producer.internals.ErrorLoggingCallback is constructed
with byte
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Attachment: (was: KAFKA-2281.patch)
> org.apache.kafka.clients.producer.internals.ErrorLoggingCallb
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Attachment: KAFKA-2281_2015-06-25.patch
> org.apache.kafka.clients.producer.internals.ErrorLoggingCallb
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Attachment: (was: KAFKA-2281.patch.1
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Attachment: KAFKA-2281.patch.1
Updated patch. Remove reference to byte[] value when logAsString is false
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Attachment: KAFKA-2281.patch
Patch submitted
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Status: Patch Available (was: Open)
> org.apache.kafka.clients.producer.internals.ErrorLoggingCallb
[
https://issues.apache.org/jira/browse/KAFKA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2281:
Description:
org.apache.kafka.clients.producer.internals.ErrorLoggingCallback is constructed
with byte
TAO XIAO created KAFKA-2281:
---
Summary:
org.apache.kafka.clients.producer.internals.ErrorLoggingCallback holds
unnecessary byte[] value
Key: KAFKA-2281
URL: https://issues.apache.org/jira/browse/KAFKA-2281
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Attachment: KAFKA-2048.patch
> java.lang.IllegalMonitorStateException thrown in AbstractFetcherThread w
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Attachment: (was: KAFKA-2048.patch)
> java.lang.IllegalMonitorStateException thrown
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Status: Patch Available (was: Open)
> java.lang.IllegalMonitorStateException thrown
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Attachment: KAFKA-2048.patch
Patch submitted. Acquire partitionMapLock explicitly before calling
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Status: Open (was: Patch Available)
> java.lang.IllegalMonitorStateException thrown
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Attachment: (was: KAFKA-2048.patch)
> java.lang.IllegalMonitorStateException thrown
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Status: Patch Available (was: Open)
> java.lang.IllegalMonitorStateException thrown
[
https://issues.apache.org/jira/browse/KAFKA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2048:
Attachment: KAFKA-2048.patch
> java.lang.IllegalMonitorStateException thrown in AbstractFetcherThread w
TAO XIAO created KAFKA-2048:
---
Summary: java.lang.IllegalMonitorStateException thrown in
AbstractFetcherThread when handling error returned from simpleConsumer
Key: KAFKA-2048
URL: https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/KAFKA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366543#comment-14366543
]
TAO XIAO edited comment on KAFKA-1997 at 3/18/15 2:5
[
https://issues.apache.org/jira/browse/KAFKA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366543#comment-14366543
]
TAO XIAO commented on KAFKA-1997:
-
[~becket_qin] I think I found a bu
[
https://issues.apache.org/jira/browse/KAFKA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2008:
Description:
The description of num.consumer.fetchers currently shown in consumer config
section of Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TAO XIAO updated KAFKA-2008:
Affects Version/s: 0.8.2.0
> Update num.consumer.fetchers description in Kafka documentat
TAO XIAO created KAFKA-2008:
---
Summary: Update num.consumer.fetchers description in Kafka
documentation
Key: KAFKA-2008
URL: https://issues.apache.org/jira/browse/KAFKA-2008
Project: Kafka
Issue
68 matches
Mail list logo
