> For this reason I'm more in favor of converting the debug.log into
async/verbose_system.log as suggested by Jeremiah and use a marker to
direct these logs (former DEBUG level logs) to that log instead.
+1
Thanks for the inclusive and considerate summary Paulo, and for the
suggestion that moves
Thanks for the constructive input and feedback! From this discussion
it seems like overloading the DEBUG level to signify
async-verbose-INFO on CASSANDRA-10241 is leading to some confusion and
we should fix this.
However, we cannot simply turn debug.log off as during CASSANDRA-10241
some verbose-b
Hi,
For CASSANDRA-13929, The patch is available for review. Anyone interested in
reviewing it?
Thanks,Jay
On Tuesday, December 12, 2017, 5:02:14 AM PST, Steinmaurer, Thomas
wrote:
Hi,
if you are talking about on-heap troubles, then the following might be related
in 3.11.x:
https://is
I've been trying to withdraw from the conversation since Friday.
-Original Message-
From: Josh McKenzie [mailto:jmcken...@apache.org]
Sent: Monday, March 19, 2018 9:56 AM
To: dev@cassandra.apache.org
Subject: Re: A JIRA proposing a seperate repository for the online documentation
And to
And to be explicit about this: I'm going to withdraw from this conversation
now. I don't think we're generating sufficient signal in this dialog
compared to the noise.
Thanks for the enthusiasm and input Kenneth.
On Mon, Mar 19, 2018 at 11:48 AM, Josh McKenzie
wrote:
> You missed the point ...
>
> You missed the point ... let them do it their way when it makes no
> difference
If you're suggesting we use a static markdown based generator as the "go
to" method for content generation and accept PR's for "New Hotness" (do it
their way), then sure, that seems a totally fair compromise. Pret
You missed the point. If someone can do a good job on something, just let them
do it their way when it makes no difference. Specifically regarding the
website, I should be able to submit HTML, CSS and JS if I want, others should
be able to do it with the static generator thing if they want. I
People seem hung up on DEBUG here. The goal of CASSANDRA-10241 was
to clean up the system.log so that it a very high “signal” in terms of what was
logged
to it synchronously, but without reducing the ability of the logs to allow
people to
solve problems and perform post mortem analysis of issues
Wow. Ok, let's try this again.
Josh, you made my point for me. Lower the barriers to entry
Kenneth, I disagree. The C* community is not expressing universal interest
in having a hand-crafted bespoke website, but many have expressed being
open to using markdown to create content. Former: high ba
Split the ticket up. Don't leave the home page broken for weeks! Move the
third party discussion to another JIRA. Get the home page fixed ASAP!
Kenneth Brotman
-Original Message-
From: Hannu Kröger [mailto:hkro...@gmail.com]
Sent: Monday, March 19, 2018 12:43 AM
To: dev@cassandra.apac
Josh, you made my point for me. Lower the barriers to entry, not throw extra
steps I don’t need at me. If someone like me offers to knock out something
that's been a problem for the group and can do a very professional job, next
time get out of the way. I don't make junk Josh. Sorry that Ap
I'd agree that INFO should be the default. Turning on the DEBUG logging
can cause notable performance issues and I would not enable it on
production systems unless I really have to. That's why I created
CASSANDRA-12696 for 4.0, so you'll be able to at least only partially
enable DEBUG based on wha
>
> In a way the real issue might be that we don’t have nightly performance
> runs that would make an accidentally introduced debug statement obvious.
First off, very much this.
Secondly, IMO it's inconsistent to leave / use assertions in a code-base as
a mix of preconditions and assertions but t
>
> I've been writing html a long time; since about 1990. You're asking me to
> learn a weird little program, a static site generator just to change
> something I can already do without using a program at all.
You're one person among a community of back-end Java devs. If you want
people to contri
Hello,
I am not developing Cassandra, but I am using it actively and helping
people to work with it. My perspective might be missing some code
considerations and history as I did not go through the ticket where this
'debug' level was added by default. But here is a feedback after upgrading
a few c
If debug log is not a real debug then you should rename it to something else,
maybe production.log. Also, I have the impression that all logs in system.log
are also contained in debug.log so it's not really useful.
I feel that be moving all verbose debug logs to trace we're losing the good
info
ah, of course. Sorry for the duplicate.
Hannu
> On 19 Mar 2018, at 09:36, kurt greaves wrote:
>
> A ticket already exists that covers this, with a patch. just needs some
> consensus around the third party page.
> https://issues.apache.org/jira/browse/CASSANDRA-14128
>
> On 19 Mar. 2018 18:26,
A ticket already exists that covers this, with a patch. just needs some
consensus around the third party page.
https://issues.apache.org/jira/browse/CASSANDRA-14128
On 19 Mar. 2018 18:26, "Hannu Kröger" wrote:
> Hello,
>
> I created this ticket
> https://issues.apache.org/jira/browse/CASSANDRA-1
Hello,
I created this ticket
https://issues.apache.org/jira/browse/CASSANDRA-14324
Basically the website front page contains manybroken links to
planetcassandra.org
Hannu
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apac
19 matches
Mail list logo
