Size of tm1s.log

[Sandhya Kumar]

Hi all,

What is the maximum size that tm1s.log can take? If it is in GB's, will TM1 be able to write transactions to this log? Is there a possibility of server crash because of that?

I found there is a parameter "MaxFileSize" in tm1s-log.properties file. If it is set to 100MB, that means tm1s.log can go only upto 100MB and further transactions will be written into a new tm1s.log saving the older one with timestamp. Is my understanding correct?

Thanks,
Sandhya

[Alan Kirk]

What is the maximum size that tm1s.log can take?

How much hard disk space have you got?

If it is in GB's, will TM1 be able to write transactions to this log?

If you have the disk space, yes.

Is there a possibility of server crash because of that?

If you run out of disk space, it's guaranteed. As soon as the server can't write to the transaction log, it drops.

I found there is a parameter "MaxFileSize" in tm1s-log.properties file. If it is set to 100MB, that means tm1s.log can go only upto 100MB and further transactions will be written into a new tm1s.log saving the older one with timestamp. Is my understanding correct?

I believe that that parameter relates to the message log, not the transaction log. The only way to get a new transaction log is to do a data save (save the cubes to disk), or do a server shutdown which does that.

[Sandhya Kumar]

Oh. Our drive has a total size of around 900 GB and we have nearly 300 GB free space.

[Alan Kirk]

Oh. Our drive has a total size of around 900 GB and we have nearly 300 GB free space.

It was a rhetorical question. IMHO regardless of whether the system allows it it would be madness to let a log file grow into gigabyte sizes. It would make searching it a nightmare, and imagine how long it would take the server to re-read it in the event of a crash. I prefer to keep them under 50 meg, and even that's during budget when the input volume is massive.