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 of crap at debug to users drives that will shorten their ssds and objectively reduce the performance of the actual database due to logging overhead for some possible day in the future when we might need them to debug a problem really we should have figured out and reproduced ourselves in the first place.
> On Mar 18, 2018, at 11:24 AM, Michael Kjellman <kjell...@apple.com> wrote: > > 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 for our users. > > >> On Mar 18, 2018, at 11:21 AM, Jonathan Ellis <jbel...@gmail.com> wrote: >> >> 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 <kjell...@apple.com> >> 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. 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 < >>> a...@thelastpickle.com> wrote: >>>> >>>> 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 easily reproduced). >>> >> >> >> >> -- >> Jonathan Ellis >> co-founder, http://www.datastax.com >> @spyced > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org >
