Hi Oren,
I understand the behavior might have changed in 3.0, but at the moment we have found several issues with 3.0 that prevent us from upgrading, so we have to continue with the current version we have installed for the moment.
I just did a test and after importing some data, 27 indexes went stale and it took about 7 hours before they became unstale again.
I hope this is not expected behavior. In case it isn't I'm not sure what to look at on our side though, the indexes have a lot of documents (our main DB size is about 1.000.000 documents), but they are not extremely complex, nor do they have cartesian products or are flattening structures (our biggest index has less than 1.000.000 documents). Could you tell me exactly what information you need?
You mentioned a few times the log file, but could you indicate which log file, where to get it (or where the documentation to get it is) and at what point (before the change, when the indexes are stale, after they become unstale, ...)?
Keep in mind that this process takes 7 hours to complete, so I can't just redo it every time a new piece of information is needed.
I hope you do understand that this seriously limits our ability to use RavenDB. It's not a case of support, SLA, ... It's a case of not having the proper documentation to know how to troubleshoot, not having proper design guidelines anywhere and having this forum as the only source of community support. I understand this is a young product, but if we are not able to build a moderate size DB with a reasonable response time on the indexes, we will have to conclude that Raven is not adequate for our needs (and this should be documented as well). So, if this is expected behavior, I hope you can be direct about it, so we can make an informed decision whether to continue with RavenDB or not (along with the other issues we posted on the forum here).