On the same page as Michael here. We disable debug logs in production due
to the performance impact. Personally I think if debug logging is necessary
for users to use the software we're doing something wrong. Also in my
experience, if something doesn't reproduce it will not get fixed. Debug
logging
Hi,
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.
A log statement that runs once or more per read or write should be easy to
spot. I haven’t measured the impact though. And as a bonus by having th
On Mon, Mar 19, 2018 at 12:41 AM, Kenneth Brotman
wrote:
> I don't know what we are doing for the website technologies right now because
> like everything else what we do is not documented anywhere. Where are the
> servers: the cloud? What server software are we running? How is the html,
> e
In Cassandra-10241 I said I was torn on this whole ticket, since most people
would end up turning it off if it had a negative impact. You said:
“I'd like to emphasize that we're not talking about turning debug or trace on
for client-generated request paths. There's way too much data generated an
It seems to me the power user who wants to eek out that last bit of
performance can do so. It also seems like the user who doesn't even know
about that is the exact kind of user that's going to need the debug log in
the future.
On Sun, Mar 18, 2018 at 1:45 PM, Michael Kjellman
wrote:
> i’m not
The answer is right before us: Let's use Rahul Singh's Awesome Cassandra list
for now: https://github.com/anant/awesome-cassandra while he works on some
other things for us. I will be submitting contributions to it regularly and
referencing it as the go to resource. It will serve us well for
First of all thanks for raising this ticket and important discussion
Alexander! See answers inline below:
> It's a tiny bit unusual to turn on debug logging for all users by default
> though, and there should be occasions to turn it on when facing issues that
> you want to debug (if they can be ea
i’m not trying to get into a fight here jeremiah. and this will be my last
reply on this as i’ve made my opinion pretty clear. but ask yourself: would you
run c* in idea debugger and then do performance testing? no. because it’s a
DEBUGger.
> On Mar 18, 2018, at 11:43 AM, J. D. Jordan wrote:
>
If there are some log messages you think should be improved to make them more
useful please do so. Saying things are “crap” is not productive.
I have seen having the extra information from the debug.log be very helpful in
debugging production issues after the fact on operational clusters many t
what really baffles me with this entire thing is as a project we don’t even log
things like partition keys along with the tombstone overwhelming or batch to
large log messages.. this would immediately be helpful to thousands and
thousands of people... yet somehow we think it’s okay to log tons o
it’s too easy to make a regression there. and does anyone even have a splunk
(or equivalent) infrastructure to actually keep debug logs around for a long
enough retention period to even have them be helpful?
again: this is something engineers for the project want. it’s not in the best
interest
That really depends on whether you're judicious in deciding what to log at
debug, doesn't it?
On Sun, Mar 18, 2018 at 12:57 PM, Michael Kjellman
wrote:
> +1. this is how it works.
>
> your computer doesn’t run at debug logging by default. your phone doesn’t
> either. neither does your smart tv.
+1. this is how it works.
your computer doesn’t run at debug logging by default. your phone doesn’t
either. neither does your smart tv. your database can’t be running at debug
just because it makes our lives as engineers easier.
> On Mar 18, 2018, at 5:14 AM, Alexander Dejanovski
> wrote:
>
Hi Paulo,
I understand the intent and Jeremiah suggested on the ticket that logging
causing performance issues should be switched to TRACE level.
It's a tiny bit unusual to turn on debug logging for all users by default
though, and there should be occasions to turn it on when facing issues that
y
I don't know what we are doing for the website technologies right now because
like everything else what we do is not documented anywhere. Where are the
servers: the cloud? What server software are we running? How is the html,
etc. generated and published? How is search done for the website?
15 matches
Mail list logo
