Couchbase Approaching full disk warning on Mac OS X - couchbase

I am trying to install Couchbase Enterprise Edition in my Mac OS X. I have followed the instruction as mentioned here. I have disabled replication and loaded sample data set beer-sample and travel-sample. But then I am getting the below warning:-
I have also seen this unanswered question.
I am having 53 GB free.
Environment:-
Mac OS X - 10.11.6
Couchbase Enterprise Edition 4.5.1

For development purposes the warning is safe to ignore. I'm not sure why it's actually occurring given the amount of free space you have - it may be getting cached somewhere.

Related

Why is it recommended to install a 32 bit server on a 64 bit machine

I was wondering to install a server on my windows machine and came to know that it is best to install a 32bit version on a 64bit machine. Is it really required.
Why is it recommended?
I want to install it for study.
Installing 32-bit software on a 64-bit machine is not recommended. No one with any credibility would make this senseless recommendation.
A major disadvantage of 32-bit software is that it cannot use more than 4GB of RAM, because memory addresses must fit into the word size of the software. This is a serious deficiency for a database server, which benefits from extra RAM.
I did consulting for a major company who was having database performance trouble. They were using Windows Server. They had been adding extra RAM DIMMs, having heard that RAM can be used to increase caching resources, but no matter how much RAM they added, it didn't help.
I logged into their site and found they were using Windows Server 32-bit. They had been spending a ton of money on RAM, but their operating system could not see it.
I listened to the YouTube video you linked to, to hear the justification of the speaker. He seems to be saying that since Windows 64-bit is backward-compatible and can run 32-bit binaries, but the reverse is not true (Windows 32-bit cannot run 64-bit binaries), he thinks you should use 32-bit binaries because they will work on both architectures.
That's bad advice.
The better advice is: Make sure you aren't using Windows 32-bit.
Come on, it's 2018. The days of 32-bit platforms is long gone.
It is definitely not required. I would say that it's not even recommended. Any 64 bit machine will be able to run a 32 bit server, however, a 32 bit server will highly underutilize the processor, especially when performing complex or graphical operations

CUDA samples cause machine to crash

I was planning on starting to use CUDA on a machine with Kubuntu 12.04 LTS and a Quadro card. I installed CUDA 5.5 using the .deb from here, and the installation seems to have gone fine. Then I built the CUDA samples, again everything went fine.
When I run the samples in sequence, however, some of them botch my display, and others simply crash my computer.
What causes the crash? How can I fix it?
I'll mention that my NVidia card is the only display adapter the machine has, but that shouldn't make CUDA crash and burn.
The problem was due to the X server using the FOSS nouveau drivers. These are known to conflict with NVidia's way of accessing the card. When I restarted X (actually, I restarted the machine), the samples did run and work properly.
Not all the samples are runnable if you just installed CUDA on a clean ubuntu system. Some of them require additional libraries, and some of them require particular CC versions.
You could read the CUDA sample document of those crashed samples for more information.
http://docs.nvidia.com/cuda/cuda-samples/index.html

MySQL ODBC on Mac OS X 10.8

I've found some problems while trying to connect to a remote MySQL database using MySQL's ODBC connector.
I'm on Mac OS X 10.8.2 and I've installed MySQL ODBC connector 5.2.4. Every time I tried to connect using this ODBC my connection gets refused.
Does anyone have the same issue? Is there any workaround?
Edit: I tested the ODBC connection with iODBC and I got the following result:
SQLDriverConnect = [iODBC][Driver Manager]dlopen(/usr/local/lib/libmyodbc5.so, 6): image not found (0) SQLSTATE=00000
SQLDriverConnect = [iODBC][Driver Manager]Specified driver could not be loaded (0) SQLSTATE=IM003
The MySQL Connector/ODBC 2.5.6 for Mac OS X comes only in versions for 10.6 (Snow Leopard) and 10.7 (Lion). I don't know about any official support from MySQL for Mac OS X versions 10.8 (Mountain Lion) or even 10.9 (Mavericks)!
Paid licensed solutions put more effort on supporting the latest Mac OS X versions... I have tried myself the evaluation version Actual ODBC Pack for Mac OS X with Mavericks and could get 3 rows per recordset. You can try that and if it works see if it's worth paying for unlimited rows.
Are you using the ODBC Administrator utility or the command line?
http://dev.mysql.com/doc/refman/5.0/en/connector-odbc-configuration-dsn-macosx.html
Edit: I don't think I noticed "remote" server. Does that remote server had a user with permissions to connect from your IP address?
#Jason Sundram (OP): Just FYI, Oracle has (in response to my filing bug reports about their documentation) updated the Mac OS X, mysql 5 installation instructions for Connector/ODBC, at:
https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation-binary-osx.html
Following those steps might be helpful. They worked for me in OS X 10.9 (Mavericks). But, I'm also not trying to do precisely what you are, with your environment, so I'm not sure what effect reinstalling as instructed there may have on your problem.

Does CouchBase (2.0.1) supports windows 32 bits?

The download page does not have a Windows build for the most recent version - 2.0.1. There is a windows 64 bits installation for the version 2.0.0.
I was wondering about the reasons of not supporting Windows 32 bits since 2.0.0 and Windows at all since 2.0.1.
Is it that they do not provide the binaries, but one could still build it for Windows 32 bits using the build instructions ?
Or there is a deeper reason, like using an API unavailable for Windows 32 bits (2.0.0) or unavailable for Windows at all (2.0.1) ?
I am asking because I am considering building it on Windows, both 32 and 64 bits, but would like to be sure the effort is not doomed to failure from the start.
we are well aware of the situation. The plan is to release 2.0.1 for 64 bits as soon as possible. We're having some delays for our Windows builds and want to make sure the quality is as high as possible. So expect a 2.0.1 64bit soon.
That said, I don't think that we'll have production ready versions of 2.0.x 32bit. What we are currently working on is a 32bit build that people can use to develop against, but is not recommended to use in production (similar to our Mac OS X builds).
I can't give you a specific timeline, but I think we're talking about "weeks". If you want to get direct feedback from one of the developers, please get in touch with Trond Norbye over twitter (#trondn).
Does this answer your question?

does mysql 5.4 has a linux 32 bit version?

Can MySQL 5.4 beta be compiled for 32-bit processors under Linux?
The current beta only has binaries for some 64-bit versions, but if you're keen on starting to beta test right now you should be able to compile from the sources on a 32-bit systems. (It IS a beta, of course, so unreliability IS to be expected -- don't run it in production, whether on 32-bit or 64-bit systems!)
According to this blog it's only available for 64-bit machines.
http://willysr.blogspot.com/2009/04/mysql-54-preview.html
or here
First, the preview release of MySQL
5.4 only includes the InnoDB scalability fixes (addressing more
CPU's/cores). Second, it is limited to
the Solaris and Linux 64-bit platforms
at this time. The other features
mentioned in this article and
additional platform support will be
appearing very shortly, so be looking
for upcoming announcements soon.
http://74.125.93.132/search?q=cache:iLgUTcXAmGUJ:mirror.facebook.com/mysql/tech-resources/articles/mysql-54.html+mysql+5.4+64bit+only&cd=9&hl=en&ct=clnk&gl=us&client=firefox-a
google cache because that website is down
if you can run ./configure and make without any errors, it should work properly.