Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default logging technique in H-Store #163

Open
priyagpssehgal opened this issue Jul 25, 2014 · 2 comments
Open

Default logging technique in H-Store #163

priyagpssehgal opened this issue Jul 25, 2014 · 2 comments

Comments

@priyagpssehgal
Copy link

Hi,
What is the default logging method in H-Store, if I do not enable "command logging" through site parameters.
Does the default logging technique try to place the log on disk? If yes, how often.

Thanks,
Priya

@apavlo
Copy link
Owner

apavlo commented Jul 27, 2014

I'm not sure what you're asking here?

H-Store now supports two different logging schemes: command logging (logical) and ARIES logging (physical). Command logging is turned on by default. ARIES has to be enabled at compile time:

http://hstore.cs.brown.edu/documentation/configuration/properties-file/site/#aries

@priyagpssehgal
Copy link
Author

Thanks Andy.
Let me try to rephrase my question.

  1. I compiled H-Store using default options/settings. Since command logging is on by default - it will get compiled.
  2. I used the default "default.properties" file and ran TPCC benchmark. I got some throughput numbers., say x.,
  3. Set site.commandlog_enable=true and rerun tpcc. For this experiment, I got the overall throughput number as say y.
  4. I found that y < x. i.e., the performance of point no.3 is less than that of point no. 2.

My question is that, in case of point 2, when we do not explicitly set site.commandlog_enable to true, is there any kind of logging that happens? If yes, how? Note that, ARIES is disabled.
If no, then we can assume that no database recovery is possible ?

Thanks,
Priya

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants