[ 
https://issues.apache.org/jira/browse/SOLR-14788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228852#comment-17228852
 ] 

Mark Robert Miller edited comment on SOLR-14788 at 11/9/20, 11:16 PM:
----------------------------------------------------------------------

This Overseer work (released from its birth into heavy historic tech debt), on 
top of the general state of everything else near this state, requires that i 
really work step by step through the system and what it does - the first time I 
saw things from that state, that perspective, I realized we don’t have adequate 
developer / user logging, it’s really not sufficient at all, and so you have to 
start adding info and debug logging, and that is very, very useful. I didn’t 
really just come to understand this wide area, but having to work through so 
much to “re-master” it, the logging i need becomes evident as I learned I 
needed it and we could just be 100x more helpful than we are.

So this time I’m not doing a great job. I’m adding here and there, over logging 
where I have to clean up, favoring finishing over a little paint outside the 
lines, blah, blah.

The takeaway really is that our system is actually fairly simple, but only if 
you axe the decade old baggage and realign some implementations. Once the 
foundation is stable, there is high value in nailing the logging.

It’s the key to letting more real help in, it’s the key for efficient test and 
user and support debugging.

We log so much data, we over log data and this thing and that thing. We should 
not over log data by default and we should log system flow really well and it 
will be a really big deal. 


was (Author: markrmiller):
This Overseer work (release it from its birth into heavy historic tech debt), 
on top of the general state of everything else near this state, requires that i 
really work step by step through the system and what it does - the first time I 
saw things from that state, that perspective, I realized we don’t have adequate 
developer / user log, it’s really not sufficient at all, and so you have to 
start adding info and debug logging, and that is very, very useful. I didn’t 
really just come to understand this wide area, but having to work through so 
much to “re-master” it, the logging i need becomes evident as I learned I 
needed it.

So this time I’m not doing a great job. I’m adding here and there, over logging 
whee I have to clean up, blah, blah.

The takeaway really is that our system is actually fairly simple, but only if 
you axe the decade old baggage and realign some implementations. Once the 
foundation is stable, there is high value in nailing the logging.

It’s the key to letting more real help in, it’s the key for efficient test and 
user and support debugging.

We log so much data, we over log data and this thing and that thing. We should 
not over log data by default and we should log system flow really well and it 
will be a really big deal. 

> Solr: The Next Big Thing
> ------------------------
>
>                 Key: SOLR-14788
>                 URL: https://issues.apache.org/jira/browse/SOLR-14788
>             Project: Solr
>          Issue Type: Task
>            Reporter: Mark Robert Miller
>            Assignee: Mark Robert Miller
>            Priority: Critical
>
> h3. 
> [!https://www.unicode.org/consortium/aacimg/1F46E.png!|https://www.unicode.org/consortium/adopted-characters.html#b1F46E]{color:#00875a}*The
>  Policeman is on duty!*{color}
> {quote}_{color:#de350b}*When The Policeman is on duty, sit back, relax, and 
> have some fun. Try to make some progress. Don't stress too much about the 
> impact of your changes or maintaining stability and performance and 
> correctness so much. Until the end of phase 1, I've got your back. I have a 
> variety of tools and contraptions I have been building over the years and I 
> will continue training them on this branch. I will review your changes and 
> peer out across the land and course correct where needed. As Mike D will be 
> thinking, "Sounds like a bottleneck Mark." And indeed it will be to some 
> extent. Which is why once stage one is completed, I will flip The Policeman 
> to off duty. When off duty, I'm always* {color:#de350b}*occasionally*{color} 
> *down for some vigilante justice, but I won't be walking the beat, all that 
> stuff about sit back and relax goes out the window.*{color}_
> {quote}
>  
> I have stolen this title from Ishan or Noble and Ishan.
> This issue is meant to capture the work of a small team that is forming to 
> push Solr and SolrCloud to the next phase.
> I have kicked off the work with an effort to create a very fast and solid 
> base. That work is not 100% done, but it's ready to join the fight.
> Tim Potter has started giving me a tremendous hand in finishing up. Ishan and 
> Noble have already contributed support and testing and have plans for 
> additional work to shore up some of our current shortcomings.
> Others have expressed an interest in helping and hopefully they will pop up 
> here as well.
> Let's organize and discuss our efforts here and in various sub issues.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to