You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by "M. Manna" <ma...@gmail.com> on 2018/05/09 13:51:27 UTC
Log Cleanup Support for Windows [KAFKA-1194]
Hello,
This issue has been outstanding for a while and impacting us both in
development and deployment time. We have had to manually build kafka core
jar and use it to work with Windows for over a year. The auto log/index
cleanup feature is very important for us on Windows because it helps us
avoid potential downtime for brokers so that they can be removed manually.
I have raised 2 pull requests so far but it was not considered at all. The
patch is quite simply but works with both Win/Linux platforms without
impacting any existing operation. The latest pull request is here
https://github.com/apache/kafka/pull/4947
I would be grateful if someone kindly considers this issue as Windows is
still a valid platform and we would like to utilise the cleanup
functionality that comes out of the box.
Regards,
Re: Log Cleanup Support for Windows [KAFKA-1194]
Posted by "M. Manna" <ma...@gmail.com>.
The tests have passed and my changes are covered by existing tests written
for LogSegmentTest. I would be grateful if someone can confirm the same.
On windows platform, some log/segment/index tests will always fail because
of the file lock/unlock issue. but they all pass on Linux. Also, the build
agent has verified the changes correctly.
Regards,
On 9 May 2018 at 16:10, Martin Gainty <mg...@hotmail.com> wrote:
> a patch could be rejected if:
>
> 1)there is no TestCase to prove the feature works
> 2)the patch causes failure in an existing testcase
> 3)the patch errors in an existing testcase
> 4)the patch works in only 1 version of OS (and doesnt work in other
> versions of OS)
> 5)implementing the patch will place a drag on existing resources
> (too many ports open/memory exhaused/diskspace exhausted)
>
>
> Have you verified 1-5 run clean?
> Martin
> ______________________________________________
>
>
>
> ------------------------------
> *From:* M. Manna <ma...@gmail.com>
> *Sent:* Wednesday, May 9, 2018 9:51 AM
> *To:* Kafka Users
> *Subject:* Log Cleanup Support for Windows [KAFKA-1194]
>
> Hello,
>
> This issue has been outstanding for a while and impacting us both in
> development and deployment time. We have had to manually build kafka core
> jar and use it to work with Windows for over a year. The auto log/index
> cleanup feature is very important for us on Windows because it helps us
> avoid potential downtime for brokers so that they can be removed manually.
>
> I have raised 2 pull requests so far but it was not considered at all. The
> patch is quite simply but works with both Win/Linux platforms without
> impacting any existing operation. The latest pull request is here
>
> https://github.com/apache/kafka/pull/4947
> <https://github.com/apache/kafka/pull/4947>
> KAFKA-1194 Forces unmapping of buffer if on Windows by mmanna-sapfgl ·
> Pull Request #4947 · apache/kafka
> <https://github.com/apache/kafka/pull/4947>
> github.com
> In response to KAFKA-1194 issue, it now forces buffer to unmap if running
> on Windows OS. Invdividual Unit Test 'testChangeFileSuffixes' on
> LogSegmentTest.scala passes. but other file IO rel...
>
>
>
> I would be grateful if someone kindly considers this issue as Windows is
> still a valid platform and we would like to utilise the cleanup
> functionality that comes out of the box.
>
> Regards,
>
Re: Log Cleanup Support for Windows [KAFKA-1194]
Posted by Martin Gainty <mg...@hotmail.com>.
a patch could be rejected if:
1)there is no TestCase to prove the feature works
2)the patch causes failure in an existing testcase
3)the patch errors in an existing testcase
4)the patch works in only 1 version of OS (and doesnt work in other versions of OS)
5)implementing the patch will place a drag on existing resources
(too many ports open/memory exhaused/diskspace exhausted)
Have you verified 1-5 run clean?
Martin
______________________________________________
________________________________
From: M. Manna <ma...@gmail.com>
Sent: Wednesday, May 9, 2018 9:51 AM
To: Kafka Users
Subject: Log Cleanup Support for Windows [KAFKA-1194]
Hello,
This issue has been outstanding for a while and impacting us both in
development and deployment time. We have had to manually build kafka core
jar and use it to work with Windows for over a year. The auto log/index
cleanup feature is very important for us on Windows because it helps us
avoid potential downtime for brokers so that they can be removed manually.
I have raised 2 pull requests so far but it was not considered at all. The
patch is quite simply but works with both Win/Linux platforms without
impacting any existing operation. The latest pull request is here
https://github.com/apache/kafka/pull/4947
[https://avatars0.githubusercontent.com/u/38857392?s=400&v=4]<https://github.com/apache/kafka/pull/4947>
KAFKA-1194 Forces unmapping of buffer if on Windows by mmanna-sapfgl · Pull Request #4947 · apache/kafka<https://github.com/apache/kafka/pull/4947>
github.com
In response to KAFKA-1194 issue, it now forces buffer to unmap if running on Windows OS. Invdividual Unit Test 'testChangeFileSuffixes' on LogSegmentTest.scala passes. but other file IO rel...
I would be grateful if someone kindly considers this issue as Windows is
still a valid platform and we would like to utilise the cleanup
functionality that comes out of the box.
Regards,