Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead. #616

akat1978 · 2021-02-09T10:49:27Z

Since yesterday without any change on package.json or code change i am getting an error at console per request.

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead.

Any ideas?

I am using latest mongoDB version (4.4.3) container image

mongo datasource

 const config = {
      name: 'mongodb',
      connector: 'mongodb',
      host: '0.0.0.0',
      port: 27017,
      user: 'user',
      password: 'xxxxx',
      database: 'database',
      useNewUrlParser: true,
};

Please advice!

wilywork · 2021-02-09T17:49:19Z

I'm getting the same error too, I use:

loopback 3.27.0,
MongoDB 4.0.4,
nodeJS 8.12.0,
loopback-connector-mongodb 5.2.2.

I didn't do any version updates, everything worked perfectly and now this message is floating around. On my local computer this message does not appear, only in Amazon's ElastichBean.

nodesocket · 2021-02-10T01:08:28Z

I believe this is just staying that use of j should be updated to use writeConcern: {}.

For example. This

let mongodbClient = new MongoClient({
    useUnifiedTopology: true,
    useNewUrlParser: true,
    connectTimeoutMS: 10000,
    poolSize: 10,
    j: true
});

Should be update to this:

let mongodbClient = new MongoClient({
    useUnifiedTopology: true,
    useNewUrlParser: true,
    connectTimeoutMS: 10000,
    poolSize: 10,
    writeConcern: {
        j: true
    }
});

See the following MongoDB Node.js documentation on WriteConcern

akat1978 · 2021-02-10T09:04:05Z

I believe this is just staying that use of j should be updated to use writeConcern: {}.

For example. This

let mongodbClient = new MongoClient({
    useUnifiedTopology: true,
    useNewUrlParser: true,
    connectTimeoutMS: 10000,
    poolSize: 10,
    j: true
});

Should be update to this:

let mongodbClient = new MongoClient({
    useUnifiedTopology: true,
    useNewUrlParser: true,
    connectTimeoutMS: 10000,
    poolSize: 10,
    writeConcern: {
        j: true
    }
});

See the following MongoDB Node.js documentation on WriteConcern

Nope, doesn't work i modify my datasource to this:

import {inject, lifeCycleObserver, LifeCycleObserver} from '@loopback/core';
import {juggler} from '@loopback/repository';

const config = {
    name: 'mongodb',
    connector: 'mongodb',
    host: '0.0.0.0',
    port: 27017,
    user: 'user',
    password: 'XXXXX',
    database: 'db_name',
    useNewUrlParser: true,
    useUnifiedTopology: true,
    writeConcern: {
        j: true,
    },
};

// Observe application's life cycle to disconnect the datasource when
// application is stopped. This allows the application to be shut down
// gracefully. The `stop()` method is inherited from `juggler.DataSource`.
// Learn more at https://loopback.io/doc/en/lb4/Life-cycle.html
@lifeCycleObserver('datasource')
export class MongodbDataSource
  extends juggler.DataSource
  implements LifeCycleObserver {
  static dataSourceName = 'mongodb';
  static readonly defaultConfig = config;

  constructor(
    @inject('datasources.config.mongodb', {optional: true})
    dsConfig: object = config,
  ) {
    super(dsConfig);
  }
}

I am still getting the same warning message "Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead."

xardit · 2021-02-10T11:09:23Z

same here on my local machine

folkmanis · 2021-02-10T12:22:47Z

Same problem. I removed option { w: 0 } from insertOne operation and - no warning!
Setting option to {writeConcern: {w: 0}} as per documentation, results in TypeScript error.

native mongodb node.js driver v3.6.4
local mongodb v4.2.11

akat1978 · 2021-02-10T13:03:10Z

Same problem. I removed option { w: 0 } from insertOne operation and - no warning!
Setting option to {writeConcern: {w: 0}} as per documentation, results in TypeScript error.

native mongodb node.js driver v3.6.4
local mongodb v4.2.11

The error is there from the beginning

> [email protected] start /Users/akat/flexcar/flexapp
> node -r source-map-support/register . "."

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead.
Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead.
Server is running at http://[::1]:3000
Try http://[::1]:3000/ping

Then after each request GET, POST, PUT, PATCH is repeated, I change the configuration as you mentioned but nothing happens

xardit · 2021-02-10T15:19:49Z

for me error on start is this:

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead.
Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead.
(node:82031) Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)

Probably something related to connector or juggler

arbourd · 2021-02-11T03:13:31Z

The deprecation warning is coming from the MongoDB driver. Was introduced in v3.6.4.

valdepeace · 2021-02-12T23:13:48Z

It is not an error it is a warning from node-mongodb-native. As @arbourd says is introduced in v3.6.4(https://github.com/mongodb/node-mongodb-native/blob/v3.6.4/lib/write_concern.js)

 * Construct a WriteConcern given an options object.
   *
   * @param {object} [options] The options object from which to extract the write concern.
   * @param {(number|string)} [options.w] **Deprecated** Use `options.writeConcern` instead
   * @param {number} [options.wtimeout] **Deprecated** Use `options.writeConcern` instead
   * @param {boolean} [options.j] **Deprecated** Use `options.writeConcern` instead
   * @param {boolean} [options.fsync] **Deprecated** Use `options.writeConcern` instead
   * @param {object|WriteConcern} [options.writeConcern] Specify write concern settings.
   * @return {WriteConcern}
   */
  static fromOptions(options) {

If not use object writeConcern return:

console.warn(
     'Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead.'
    );
    return new WriteConcern(
      options.w,
      options.wtimeout,
      options.j || options.journal,
      options.fsync
    );

and loopback-connector-mongodb not implemented is option in validOptionNames https://github.com/strongloop/loopback-connector-mongodb/blob/master/lib/mongodb.js:

 // See https://github.com/mongodb/node-mongodb-native/blob/3.0.0/lib/mongo_client.js#L37
    const validOptionNames = [
      'poolSize',
      'ssl',
      'sslValidate',
      'sslCA',
      'sslCert',
      'sslKey',
      'sslPass',
      'sslCRL',
      'autoReconnect',
      'noDelay',
      'keepAlive',
      'keepAliveInitialDelay',
      'connectTimeoutMS',
      'serverSelectionTimeoutMS',
      'family',
      'socketTimeoutMS',
      'reconnectTries',
      'reconnectInterval',
      'ha',
      'haInterval',
      'replicaSet',
      'secondaryAcceptableLatencyMS',
      'acceptableLatencyMS',
      'connectWithNoPrimary',
      'authSource',
      'w',
      'wtimeout',
      'j',
      'forceServerObjectId',
      'serializeFunctions',
      'ignoreUndefined',
      'raw',
      'bufferMaxEntries',
      'readPreference',
      'pkFactory',
      'promiseLibrary',
      'readConcern',
      'maxStalenessSeconds',
      'loggerLevel',
      'logger',
      'promoteValues',
      'promoteBuffers',
      'promoteLongs',
      'domainsEnabled',
      'checkServerIdentity',
      'validateOptions',
      'appname',
      'auth',
      'user',
      'password',
      'authMechanism',
      'compression',
      'fsync',
      'readPreferenceTags',
      'numberOfRetries',
      'auto_reconnect',
      'minSize',
      'useNewUrlParser',
      'useUnifiedTopology',
      // Ignored options
      'native_parser',
      // Legacy options
      'server',
      'replset',
      'replSet',
      'mongos',
      'db',
    ];

nodesocket · 2021-02-13T01:16:12Z

@valdepeace I understand the warning is coming from the MongoDB Node.js driver, but updating my MongoClient() constructor to:

    writeConcern: {
        j: true
    }

Still get's me Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead logged. I don't see j: true used anywhere else.

nodesocket · 2021-02-13T04:50:58Z

I've created an official bug report on the Jira for the Node.js driver at https://jira.mongodb.org/browse/NODE-3114 if anybody wants to follow along or chime in.

BoLaMN · 2021-02-15T09:36:40Z

its definitely the db.collection call if you change

MongoDB.prototype.collection = function(modelName) {
  if (!this.db) {
    throw new Error(g.f('{{MongoDB}} connection is not established'));
  }
  const collectionName = this.collectionName(modelName);
  return this.db.collection(collectionName);
};

to include the writeConcern object

MongoDB.prototype.collection = function(modelName) {
  if (!this.db) {
    throw new Error(g.f('{{MongoDB}} connection is not established'));
  }
  const collectionName = this.collectionName(modelName);
  return this.db.collection(collectionName, { writeConcern: { w: null } });
};

it stops complaining would have todo the same with the ping function as it calls db.collection directly

pitor · 2021-02-17T21:39:07Z

As a temporary hack before we get a proper fix, I have added the prototype function from previous comment to my server/datasources.local.js

It gets rid of most of the warnings.

let mongoConnector = require('loopback-connector-mongodb');
let MongoDB = mongoConnector.MongoDB;

MongoDB.prototype.collection = function(model) {
    if (!this.db) {
      throw new Error(g.f('{{MongoDB}} connection is not established'));
    }
    var collectionName = this.collectionName(model);
    return this.db.collection(collectionName, { writeConcern: { w: null } });
  };

wolrajhti · 2021-02-18T08:53:36Z

I just submit a PR to node-mongodb-native driver to fix the merging of writeConcern mongodb/node-mongodb-native#2744 which stop warning outputs.

An other PR is related to our topic and will remove the warnings mongodb/node-mongodb-native/pull/2743

RAI-shyam · 2021-03-08T17:23:59Z

@wolrajhti , curious I see the PRs merged, but I'm still seeing the issue on my end, did mongodb 3.6.4 get updated or will a new version needs to be released?

wolrajhti · 2021-03-09T08:15:43Z

@RAI-shyam A fix has been done on the branch 3.6 of the mongodb driver, it will be available when they will released 3.6.5 (or 3.7). hopefully very soon 🤞

ashwinsoni · 2021-04-16T12:43:53Z

Updating the version to 5.5.0 worked for me. Thanks for contributing :)

"loopback-connector-mongodb": "^5.5.0"

Adimvicky · 2021-04-26T22:17:57Z

Updating the version to 5.5.0 worked for me. Thanks for contributing :)
"loopback-connector-mongodb": "^5.5.0"

Hey @ashwinsoni. My package.json shows i'm already using "v5.5.0" but i still get this warning.

akkapur · 2021-04-27T18:10:32Z

Updating to version 6.0.0 resolves this for me.

"loopback-connector-mongodb": "^6.0.0",

Adimvicky · 2021-04-27T18:28:38Z

Thanks @akkapur! Upgrading to version 6.0.0 resolves it for me as as well.

ashwinsoni · 2021-05-01T18:49:59Z

@Adimvicky Sorry about that, seems like the modules were not cleaned and rebuild after updating to 5.5.0 on your machine.

But I'm happy that 6.0.0 did worked for you :)

chiholiu10 · 2021-05-06T23:58:37Z

try add this one useUnifiedTopology: true

stale · 2021-07-14T00:01:00Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale · 2021-07-28T00:19:24Z

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

akat1978 added the question label Feb 9, 2021

wolrajhti mentioned this issue Feb 14, 2021

Update mongodb to ^3.6.4 #618

Merged

5 tasks

sibelius mentioned this issue Mar 17, 2021

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead. Automattic/mongoose#10009

Closed

mingchuno mentioned this issue Jun 10, 2021

collection.deleteMany() being called in a deprecated way, yielding a mongoDB Driver warning jdesboeufs/connect-mongo#422

Closed

stale bot added the stale label Jul 14, 2021

stale bot closed this as completed Jul 28, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead. #616

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead. #616

akat1978 commented Feb 9, 2021 •

edited

Loading

wilywork commented Feb 9, 2021 •

edited

Loading

nodesocket commented Feb 10, 2021 •

edited

Loading

akat1978 commented Feb 10, 2021 •

edited

Loading

xardit commented Feb 10, 2021 •

edited

Loading

folkmanis commented Feb 10, 2021

akat1978 commented Feb 10, 2021 •

edited

Loading

xardit commented Feb 10, 2021

arbourd commented Feb 11, 2021 •

edited

Loading

valdepeace commented Feb 12, 2021

nodesocket commented Feb 13, 2021 •

edited

Loading

nodesocket commented Feb 13, 2021

BoLaMN commented Feb 15, 2021

pitor commented Feb 17, 2021

wolrajhti commented Feb 18, 2021

RAI-shyam commented Mar 8, 2021 •

edited

Loading

wolrajhti commented Mar 9, 2021

ashwinsoni commented Apr 16, 2021

Adimvicky commented Apr 26, 2021

akkapur commented Apr 27, 2021

Adimvicky commented Apr 27, 2021

ashwinsoni commented May 1, 2021

chiholiu10 commented May 6, 2021

stale bot commented Jul 14, 2021

stale bot commented Jul 28, 2021

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead. #616

Top-level use of w, wtimeout, j, and fsync is deprecated. Use writeConcern instead. #616

Comments

akat1978 commented Feb 9, 2021 • edited Loading

wilywork commented Feb 9, 2021 • edited Loading

nodesocket commented Feb 10, 2021 • edited Loading

akat1978 commented Feb 10, 2021 • edited Loading

xardit commented Feb 10, 2021 • edited Loading

folkmanis commented Feb 10, 2021

akat1978 commented Feb 10, 2021 • edited Loading

xardit commented Feb 10, 2021

arbourd commented Feb 11, 2021 • edited Loading

valdepeace commented Feb 12, 2021

nodesocket commented Feb 13, 2021 • edited Loading

nodesocket commented Feb 13, 2021

BoLaMN commented Feb 15, 2021

pitor commented Feb 17, 2021

wolrajhti commented Feb 18, 2021

RAI-shyam commented Mar 8, 2021 • edited Loading

wolrajhti commented Mar 9, 2021

ashwinsoni commented Apr 16, 2021

Adimvicky commented Apr 26, 2021

akkapur commented Apr 27, 2021

Adimvicky commented Apr 27, 2021

ashwinsoni commented May 1, 2021

chiholiu10 commented May 6, 2021

stale bot commented Jul 14, 2021

stale bot commented Jul 28, 2021

akat1978 commented Feb 9, 2021 •

edited

Loading

wilywork commented Feb 9, 2021 •

edited

Loading

nodesocket commented Feb 10, 2021 •

edited

Loading

akat1978 commented Feb 10, 2021 •

edited

Loading

xardit commented Feb 10, 2021 •

edited

Loading

akat1978 commented Feb 10, 2021 •

edited

Loading

arbourd commented Feb 11, 2021 •

edited

Loading

nodesocket commented Feb 13, 2021 •

edited

Loading

RAI-shyam commented Mar 8, 2021 •

edited

Loading