Using docker is probably the best option.

The one thing I cannot confirm (and I haven't tried yet) is how the volumes
will behave when you are transferring the topic log offsets to your windows
drive. Hopefully, this will be fine
but do let us know if someone has tried.

Thanks,



On 7 August 2018 at 23:33, jan <rtm4...@googlemail.com.invalid> wrote:

> @Jacob Sheck: It was 18 months ago so I don't recall but I was told
> clearly windows ain't supported when I reported problems.
>
> I don't know if my problems were down to my inexperience or my use of
> windows, but I basically assuming I was controlling for one variable
> (n00bish inexperience) but was informed I now had two (n00bness, and
> an unsupported platform).
>
> tl;dr if it doesn't work on X, we need to say so clearly. It's just...
> good manners, surely?
>
> cheers
>
> jan
>
>
> On 07/08/2018, M. Manna <manme...@gmail.com> wrote:
> > By fully broken, i mean not designed and tested to work on Windows.
> >
> > On Tue, 7 Aug 2018, 16:34 M. Manna, <manme...@gmail.com> wrote:
> >
> >> Log Cleaner functionality is fully broken... If you haven't tried that
> >> already.
> >>
> >>
> >>
> >> On 7 Aug 2018 4:24 pm, "Jacob Sheck" <shec0...@gmail.com> wrote:
> >>
> >> While I agree that it is less frustrating to run Kafka on Linux, I am
> >> interested to hear what specific issues you are running into on windows?
> >>
> >>
> >> On Tue, Aug 7, 2018 at 9:42 AM jan <rtm4...@googlemail.com.invalid>
> >> wrote:
> >>
> >> > This is an excellent suggestion and I intend to do so henceforth
> >> > (thanks!), but it would be an adjunct to my request rather than the
> >> > answer; it still needs to be made clear in the docs/faq that you
> >> > *can't* use windows directly.
> >> >
> >> > jan
> >> >
> >> > On 07/08/2018, Rahul Singh <rahul.xavier.si...@gmail.com> wrote:
> >> > > I would recommend using Docker — it would end up being run on a
> Linux
> >> > kernel
> >> > > VM on windows and is easier to get started on with a bit of learning
> >> > curve
> >> > > for Docker. Less time wasted overall and at least at that point you
> >> would
> >> > > know Docker.
> >> > >
> >> > > Rahul
> >> > > On Aug 7, 2018, 4:50 AM -0400, jan <rtm4...@googlemail.com.
> invalid>,
> >> > wrote:
> >> > >> I tried using it just for learning a while back and wasted 3 days
> >> > >> because it's not supported on windows. Even basic stuff didn't
> work.
> >> > >> I
> >> > >> did read the docs first!
> >> > >>
> >> > >> I think I've seen other people on this list have questions
> >> > >> about/problems for exactly the same reason, and that could be a lot
> >> > >> of
> >> > >> time saved if it was in the docs - it needs to be. So how do I ask
> >> > >> the
> >> > >> maintainers to put 'No, Not Windows" in there?
> >> > >> Serious question.
> >> > >>
> >> > >> I resent losing 3 days of work because of essential missing info.
> It
> >> > >> sounds like (compared to @M. Manna) that I got off lightly.
> >> > >>
> >> > >> So can we put a clear caveat in the documentation, please, right at
> >> the
> >> > >> top?
> >> > >>
> >> > >> jan
> >> > >>
> >> > >> On 07/08/2018, M. Manna <manme...@gmail.com> wrote:
> >> > >> > The answer is - Absolutely not. If you don’t have Linux rack, or
> >> > >> > Kubernetes
> >> > >> > deployment -it will not work on Windows as guaranteed.
> >> > >> >
> >> > >> > I know this because I have tried to make it work for the past 1
> >> year.
> >> > >> > File
> >> > >> > handling always fails and crashes the cluster on Windows.
> >> > >> >
> >> > >> > Thanks,
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> > On Tue, 7 Aug 2018 at 01:54, Alew <ale...@gmail.com> wrote:
> >> > >> >
> >> > >> > > Hi!
> >> > >> > >
> >> > >> > > Is it recommended to use production Kafka cluster on Windows?
> >> > >> > >
> >> > >> > > Can't get it from the documentation. It is possible to start
> >> > >> > > Kafka
> >> > on
> >> > >> > > Windows, but maybe it's for development purposes only.
> >> > >> > >
> >> > >> > > Thanks.
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >
> >> >
> >>
> >>
> >>
> >
>

Reply via email to