Re: Re[2]: Asynchronous registration of binary metadata

2019-08-15 Thread Sergey Chugunov
Denis, Thanks for bringing this issue up, decision to write binary metadata from discovery thread was really a tough decision to make. I don't think that moving metadata to metastorage is a silver bullet here as this approach also has its drawbacks and is not an easy change. In addition to workar

Re[2]: Asynchronous registration of binary metadata

2019-08-14 Thread Zhenya Stanilovsky
> >> 1. Yes, only on OS failures. In such case data will be received from alive >> nodes later. What behavior would be in case of one node ? I suppose someone can obtain cache data without unmarshalling schema, what in this case would be with grid  operability? > >> 2. Yes, for walmode=FSYNC wri

Re: Re[2]: Asynchronous registration of binary metadata

2019-08-14 Thread Павлухин Иван
Denis, Several clarifying questions: 1. Do you have an idea why metadata registration takes so long? So poor disks? So many data to write? A contention with disk writes by other subsystems? 2. Do we need a persistent metadata for in-memory caches? Or is it so accidentally? Generally, I think that

Re[2]: Asynchronous registration of binary metadata

2019-08-14 Thread Zhenya Stanilovsky
Alexey, but in this case customer need to be informed, that whole (for example 1 node) cluster crash (power off) could lead to partial data unavailability. And may be further index corruption. 1. Why your meta takes a substantial size? may be context leaking ? 2. Could meta be compressed ? >Сред