[
https://issues.apache.org/jira/browse/CASSANDRA-15586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070863#comment-17070863
]
Stefan Miklosovic edited comment on CASSANDRA-15586 at 3/30/20, 10:37 AM:
--------------------------------------------------------------------------
I was testing alpha3 on FreeBSD 12.1 and openjdk 11 and it worked with some
caveats. As you probably know, there is a system of "ports" in FreeBSD which
are basically vanilla binary packages / sources which are taken and repackaged
to be comaptible what FreeBSD runs with.
There is currently only Cassandra 3 port of version 3.11.6 which is taken care
of by one of a FreeBSD port commiter. I think that the porting work will be
done similarly for 4.0 once it is out but I can contact that person on my
behalf to know more details and maybe I will even contribute that myself.
When it comes to tarball of alpha3, it worked but there was one stacktrace
about not having epoll on FreeBSD and that it is skipped but otherwise I was
able to connect to it and so on and it seemed to behave just fine. I was trying
to install Linux compatibility layer (official thingy from FreeBSD) but the
result was just same.
My line of thought here is to try to provide Cassandra 4.0 port as there is for
Cassandra 3 already. If nobody objects and seems this effort worthy, I might
start to hack around that ...
FreeBSD port: [https://svnweb.freebsd.org/ports/head/databases/cassandra3/]
was (Author: stefan.miklosovic):
I was testing alpha3 on FreeBSD 12.1 and it worked with some caveats. As you
probably know, there is a system of "ports" in FreeBSD which are basically
vanilla binary packages / sources which are taken and repackaged to be
comaptible what FreeBSD runs with.
There is currently only Cassandra 3 port of version 3.11.6 which is taken care
of by one of a FreeBSD port commiter. I think that the porting work will be
done similarly for 4.0 once it is out but I can contact that person on my
behalf to know more details and maybe I will even contribute that myself.
When it comes to tarball of alpha3, it worked but there was one stacktrace
about not having epoll on FreeBSD and that it is skipped but otherwise I was
able to connect to it and so on and it seemed to behave just fine. I was trying
to install Linux compatibility layer (official thingy from FreeBSD) but the
result was just same.
My line of thought here is to try to provide Cassandra 4.0 port as there is for
Cassandra 3 already. If nobody objects and seems this effort worthy, I might
start to hack around that ...
FreeBSD port: [https://svnweb.freebsd.org/ports/head/databases/cassandra3/]
> 4.0 quality testing: Cluster Setup and Maintenance
> --------------------------------------------------
>
> Key: CASSANDRA-15586
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15586
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
> Reporter: Josh McKenzie
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Labels: 4.0-QA
> Fix For: 4.0-rc
>
>
> We want 4.0 to be easy for users to setup out of the box and just work. This
> means having low friction when users download the Cassandra package and start
> running it. For example, users should be able to easily configure and start
> new 4.0 clusters and have tokens distributed evenly. Another example is
> packaging, it should be easy to install Cassandra on all supported platforms
> (e.g. packaging) and have Cassandra use standard platform integrations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
