Opened 9 years ago
Closed 9 years ago
#1153 closed enhancement (fixed)
Too much log of grpc in petascope.log
Reported by: | Bang Pham Huu | Owned by: | Alex Toader |
---|---|---|---|
Priority: | major | Milestone: | 9.2 |
Component: | petascope | Version: | development |
Keywords: | petascope | Cc: | Alex Dumitru, George Merticariu, Alex Toader |
Complexity: | Medium |
Description
There are too much periodical log in petascope.log and it makes really hard to know what is the problem from petascope. I can suggest make another log file for this information (e.g grpc.log) and keep petascope.log only store what belongs to it.
http, content-type: application/grpc, te: trailers, user-agent: grpc-java-netty], streamDependency=0, weight=16, exclusive=false, padding=0, endStream=false ------------------------------------ [18:25:19] DEBUG NettyClientTransport@71: ----------------OUTBOUND-------------------- DATA: streamId=11, padding=0, endStream=true, length=58, bytes=00000000350a2462356137636231632d363730622d346162362d626432622d34656337323361623663396410ffd6e494071a0752415342415345 ------------------------------------ [18:25:19] DEBUG NettyClientTransport@71: ----------------INBOUND-------------------- HEADERS: streamId=11, headers=DefaultHttp2Headers[:status: 200, grpc-encoding: identity, grpc-accept-encoding: identity,deflate,gzip, content-type: application/grpc], padding=0, endStream=false
Change History (6)
follow-up: 3 comment:1 by , 9 years ago
comment:2 by , 9 years ago
The random ID is the server identifier. I can change this, but it will take more than a day.
I will look into removing GRPC's log.
comment:3 by , 9 years ago
Replying to bphamhuu:
@Alex: I also think there is problem with "random" string in log file name (before at least I can see as N1 - N9). Now everything is random file name (it has > 1000 log files now. So I suggest keep the file log as servername_ + time start server .log
and when stop_rasdaman.sh collect all of log files to a directory name log_timestop to backup. (TimeStart and TimeStop is DateTime).
May be you can have another choice, but remove the number of logs to generate periodically and make it understandable. Do you agree?
Bang please open a new ticket, this is a separate thing (and put it on super low priority).
comment:5 by , 9 years ago
I do not know how to fix it at the moment. The log output is not something we set but something set by a third party library.
comment:6 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This was fixed by a patch Alex Dumitru sent.
@Alex: I also think there is problem with "random" string in log file name (before at least I can see as N1 - N9). Now everything is random file name (it has > 1000 log files now. So I suggest keep the file log as servername_ + time start server .log
and when stop_rasdaman.sh collect all of log files to a directory name log_timestop to backup. (TimeStart and TimeStop is DateTime).
May be you can have another choice, but remove the number of logs to generate periodically and make it understandable. Do you agree?